Quality of service for device assisted services

ABSTRACT

Quality of Service (QoS) for Device Assisted Services (DAS) are provided. In some embodiments, QoS for DAS includes providing a wireless communications device configures to determine a QoS request for a service over a wireless network; and verifying the QoS request for the service over the wireless network using one or more verification techniques.

CROSS REFERENCE TO OTHER APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 61/206,354 entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHODfiled Jan. 28, 2009, U.S. Provisional Patent Application No. 61/206,944(entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 4,2009, U.S. Provisional Application No. 61/207,393 entitled SERVICESPOLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 10, 2009, U.S.Provisional Patent Application No. 61/207,739 entitled SERVICES POLICYCOMMUNICATION SYSTEM AND METHOD filed on Feb. 13, 2009, U.S. ProvisionalPatent Application No. 61/252,151 entitled SECURITY TECHNIQUES FORDEVICE ASSISTED SERVICES, filed on Oct. 15, 2009, and U.S. ProvisionalPatent Application No. 61/252,153 entitled DEVICE GROUP PARTITIONS ANDSETTLEMENT PLATFORM filed on Oct. 15, 2009, which are incorporatedherein by reference for all purposes.

This application is a continuation in part of co-pending U.S. patentapplication Ser. No. 12/380,780 , entitled AUTOMATED DEVICE PROVISIONINGAND ACTIVATION, filed on Mar. 2, 2009, which is incorporated herein byreference for all purposes, and which claims priority to U.S.Provisional Patent Application No. 61/206,354 entitled SERVICES POLICYCOMMUNICATION SYSTEM AND METHOD filed Jan. 28, 2009, U.S. ProvisionalPatent Application No. 61/206,944 entitled SERVICES POLICY COMMUNICATIONSYSTEM AND METHOD filed Feb. 4, 2009, U.S. Provisional Application No.61/207,393 entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHODfiled Feb. 10, 2009, and U.S. Provisional Patent Application No.61/207,739 entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHODfiled on Feb. 13, 2009, which are incorporated herein by reference forall purposes.

BACKGROUND OF THE INVENTION

With the advent of mass market digital communications, applications andcontent distribution, many access networks such as wireless networks,cable networks and DSL (Digital Subscriber Line) networks are pressedfor user capacity, with, for example, EVDO (Evolution-Data Optimized),HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax(Worldwide Interoperability for Microwave Access), DOCSIS, DSL, andWi-Fi (Wireless Fidelity) becoming user capacity constrained. In thewireless case, although network capacity will increase with new highercapacity wireless radio access technologies, such as MIMO(Multiple-Input Multiple-Output), and with more frequency spectrum andcell splitting being deployed in the future, these capacity gains arelikely to be less than what is required to meet growing digitalnetworking demand.

Similarly, although wire line access networks, such as cable and DSL,can have higher average capacity per user compared to wireless, wireline user service consumption habits are trending toward very highbandwidth applications and content that can quickly consume theavailable capacity and degrade overall network service experience.Because some components of service provider costs go up with increasingbandwidth, this trend will also negatively impact service providerprofits.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 illustrates a functional diagram of a network architecture forproviding quality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments.

FIG. 2 illustrates another functional diagram of another networkarchitecture for providing quality of service (QoS) for device assistedservices (DAS) in accordance with some embodiments.

FIG. 3 illustrates a functional diagram of an architecture for includinga device based service processor and a service controller for providingquality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments.

FIGS. 4A through 4C illustrates a functional diagram for providingquality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments.

FIG. 5 illustrates a functional diagram for generating a QoS activitymap for quality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments.

FIG. 6 illustrates a functional diagram for quality of service (QoS) fordevice assisted services for an end to end coordinated QoS servicechannel control in accordance with some embodiments.

FIG. 7 illustrates a flow diagram for quality of service (QoS) fordevice assisted services (DAS) in accordance with some embodiments.

FIGS. 8A through 8C each illustrate another flow diagram for quality ofservice (QoS) for device assisted services (DAS) in accordance with someembodiments.

FIG. 9 illustrates another flow diagram for quality of service (QoS) fordevice assisted services (DAS) in accordance with some embodiments.

FIG. 10 illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.

FIG. 11 illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.

FIG. 12 illustrates a device stack for providing various service usagemeasurement techniques in accordance with some embodiments.

FIG. 13 illustrates another device stack for providing various serviceusage measurement techniques in accordance with some embodiments.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

As wireless networks, such as mobile networks, evolve towards higherbandwidth services, which can include or require, for example, variouslevels of Quality of Service (QoS) (e.g., conversational, interactivedata, streaming data, and/or various (end-to-end) real-time servicesthat may benefit from QoS), demands will increase for converged networkservices to facilitate such services for end-to-end services betweennetworks (e.g., to allow for control and/or support for such services,for example, QoS support, across network boundaries, such as betweenwireless networks (such as various service provider networks) and IPnetworks (such as the Internet), and/or other networks). While variousefforts have attempted to address such QoS needs, such as policymanagement frameworks for facilitating QoS end-to end solutions, thereexists a need to facilitate various QoS requirements using DeviceAssisted Services (DAS).

Accordingly, Quality of Service (QoS) for Device Assisted Services (DAS)is provided. In some embodiments, QoS for DAS is provided.

To establish a QoS channel, differentiated services are typicallyavailable, in which one class/level of service has a higher prioritythan another to provide for differentiated services on a network, suchas a wireless network. For example, in a wireless network, variousnetwork elements/functions can be provisioned and controlled toestablish a single end or end to end QoS channel. In some embodiments, acentralized QoS policy coordination and decision function using DAStechniques to assist in coordinating the QoS channel setup and controlamong the various elements of a wireless network is provided.

In some embodiments, QoS channel refers to the logical communicationchannel connected to a device that provides a desired level of QoSservice level. For example, the QoS channel can be created with one ormore QoS links, in which each link represents a QoS enabled connectionthat spans a portion of the total end to end network communication pathfrom a near end device to a far end device. For example, the far enddevice can be on the same network or on a different network, potentiallywith different access technology and/or a different access networkcarrier. In some embodiments, the QoS channel includes one or more QoSlinks in which each link in the channel is QoS enabled, or one or moreof the links in the channel is QoS enabled and others are not. As anexample, a QoS channel can include the following links: a first devicetraffic path link, a first device to access network equipment elementlink (e.g., 2G/3G/4G wireless base station, WiFi access point, cablenetwork head end, DSLAM, fiber aggregation node, satellite aggregationnode, or other network access point/node), a first carrier core network,a long haul IPX network, a second carrier core network, a second deviceto access network equipment element link, and a second device trafficpath link as similarly described herein with respect to variousembodiments.

In some embodiments, each of the links described above have the abilityto provide QoS services for that segment of an overall QoS channel. Insome embodiments, the device traffic path link and/or the device toaccess network equipment element link are QoS enabled, but the carriercore network and/or IPX network links are not QoS enabled. In someembodiments, the core network and/or IPX network have sufficientover-provisioning of bandwidth that QoS is not limited by these networkelements and, for example, can be limited by the device traffic linkand/or the device to access network equipment element link do not havesufficient excess bandwidth making it desirable to QoS enable these QoSchannel links. A common example is a 2G/3G/4G wireless network in whicha device traffic path link and the device to access network element link(e.g., Radio Access Bearer (RAB)) are QoS enabled while the carrier corenetwork and IPX network links are not (e.g., are provided at a besteffort service level or other service levels).

In some embodiments, a QoS session refers to the QoS enabled traffic fora given device that flows over a QoS channel or QoS link. This QoStraffic supports a QoS service activity. In some embodiments, a QoSservice activity includes a device service usage that is requested,configured, or preferably serviced with a given level of QoS. In someembodiments, a device QoS activity is a combination of one or more ofthe following: application, destination, source, URL or other similarservice identifier, service provider, network type, traffic type,content type, network protocol, session type, QoS identifier, time ofday, network capacity (e.g., network busy state), user service planauthorization or standing, roaming/home network status, and/or othercriteria/measures as similarly described herein. For example, QoSservice activities that are supported by QoS sessions can include VOIPtraffic, streaming video traffic, differentiated access bandwidth duringbusy network periods, real-time interactive traffic, such as networkconnected multimedia meetings (e.g., shared presentations, picture,video, voice, and/or other such applications/services), best effortinteractive, such as Internet browsing, time sensitive services, such asemail message body delivery, near real time interactive services, suchas SMS or push to talk, background download services, such as emaildownloads and other file transfers (e.g., FTP), and/or truly backgrounddownload services, such as software updates.

In some embodiments, various QoS levels or classes are supported. Forexample a conversation class can provide for real-time traffic, which istypically very delay sensitive but can tolerate bit errors and packetlosses. The conversational class is typically used for Voice Over IP(VOIP) and video telephony, in which users of such services benefit fromthe short delay features of the conversational class. A streaming classis similar to the conversational class except that the streaming classtypically can tolerate more delay than the conversational class. Thestreaming class is generally used for when one end of the connection isa user (e.g., human user) and the other end is a machine/computer (e.g.,for streaming content applications, such as streaming of video, such asmovies or other video content). An interactive class is generallyintended for traffic that allows delay variation while requiringreasonably low response time (e.g., web browsing or other applicationsin which the channel can be unused for long periods of time but when auser makes a request for a new page/data, the response time should bereasonably low). A background class is generally used for lowestpriority service usages (e.g., typically used for e-mail, softwareupdates, and/or other similar applications). In some embodiments,various QoS classes or services are applicable to the conversationalclass. In some embodiments, various QoS classes or services are alsoapplicable to the streaming class. In some embodiments, various QoSclasses or services are also applicable to the interactive class buttypically not applicable to the background class. As will now beapparent to one of ordinary skill in the art, various other classes canbe provided with lower or higher granularity based on serviceusage/channel requirements and/or network architectures.

In some embodiments, a QoS link or a QoS channel supports one QoSsession. In some embodiments, a QoS link or a QoS channel supportsmultiple QoS sessions. In some embodiments, QoS link provisioning isprovided to setup the QoS traffic level for a given QoS session or groupof QoS sessions.

In some embodiments, a QoS channel is a single ended QoS channel or anend to end QoS channel. For example, if a QoS channel is end to end,then the QoS channel provisioning is accomplished in a coordinatedmanner for each QoS enabled link in the QoS channel. If a QoS channel issingle ended, then the network elements and/or device participate inprovisioning as much of one end of the QoS channel as possible, leavingprovisioning of the QoS for the other end of the channel as theresponsibility of the device and/or network elements that handle thetraffic at the other end of the QoS channel. In some embodiments, asingle ended QoS channel includes another single ended QoS channel atthe other end. In some embodiments, only one end has single ended QoSchannel enablement while the other end of the channel is a best effortservice level, which, for example, can be used where one end of the QoSchannel has tighter constraints on traffic capacity or quality than theother end (e.g., a VOIP call with one end that is QoS enabled on a 3Gwireless network that has relatively tight bandwidth compared to alightly loaded cable modem network device on the other end which may notneed to be QoS enabled in order to achieve adequate voice quality).

In some embodiments, a QoS request (e.g., a QoS channel request or QoSservice request) is a request for a QoS provisioning event to enable aQoS channel for one or more QoS service activities. In some embodiments,QoS availability assessment includes determining whether one or more ofthe links in a possible QoS channel are available (e.g., based onnetwork capacity and transmission quality) to provision the necessarylevel of QoS for a requested QoS channel. In some embodiments, a QoSrequest is initiated by a device, a user, an application, and/or anetwork element/function as similarly described herein.

In some embodiments, a service plan refers to the collection of accessservice capabilities and/or QoS capabilities that are associated with acommunications device. In some embodiments, the access and/or QoScapabilities are determined by the collection of access service controlpolicies for the device. In some embodiments, these service controlpolicies are implemented in the network equipment. In some embodiments,these access service control policies are implemented both in the deviceand in the network equipment. In some embodiments, these access servicecontrol policies are implemented in the device. In some embodiments,there are different levels of service control capabilities (e.g.,policies) based on different levels of service plan payments or devicestanding or user standing. In some embodiments, there are differentlevels of service control policies based on network type, time of day,network busy status, and/or other criteria/measures as similarlydescribed herein with respect to various embodiments. In someembodiments, the access control and QoS control policies are based onthe type of service activity being sought. In some embodiments, the QoSlevel and access level available for a given service activity for agiven device or user is determined by the policies associated with theservice plan. In some embodiments, a QoS authorization assessment isperformed to determine whether a device or user has sufficient serviceplan standing to allow the requested level of QoS.

In some embodiments, before a QoS channel or link is provisioned (orbefore a QoS request is responded to or filled), a QoS availabilityassessment is performed to determine whether sufficient communicationchannel resources are available to provision the necessary level of QoSfor the QoS channel or link. In some embodiments, this QoS availabilityassessment is determined by assessing the available QoS capacity for oneor more necessary QoS links in the channel. For example, the availableQoS link capacity can be assessed for one or more of a device trafficpath, a device to access network equipment element link, a core networklink, and/or an IPX network link. If the QoS assessment shows that thenecessary channel capacity and quality is available for the desired QoSlevel for one or more desired QoS service activities, then a QoS channelrequest or QoS service request can be granted. In some embodiments, aQoS link or QoS channel reservation process is provided to reserve QoScapacity and quality in advance of link or channel provisioning toensure that the available QoS resources are not assigned between thetime of QoS availability assessment and QoS channel provisioning.

In some embodiments, the QoS availability assessment is performed afterQoS authorization assessment. This prevents the unnecessary exercisingof network elements when the device or user does not have sufficientservice plan standing to receive the desired level of QoS even if it isavailable. This can be an important screening function performed on thedevice in the service processor, or by a centralized network functionsuch as the service controller (e.g., or interchangeably, the homeagent(HA), Homer Location Register (HLR), Authentication, Authorization,and Accounting (AAA) server/gateway/function, base station, one of thegateways or other network element/function). In some embodiments, QoSavailability is assessed without conducting a QoS authorizationassessment or before receiving the response to a QoS authorizationassessment.

In some embodiments, a QoS channel is provisioned to create the QoSchannel to support a QoS session (e.g., a QoS service activity). In someembodiments, QoS channel provision includes assigning, routing, and/orotherwise causing the QoS session traffic to flow over one or more QoSlinks in the assigned QoS channel.

In some embodiments, device assisted service traffic control and QoSapply readily and directly to the problems of managing a QoS device linkfor QoS channel provisioning. Accordingly, in some embodiments, aservice provider is provided to assist in provisioning the deviceportion of the QoS channel. In some embodiments, the service processorprovisions the device link portion of the QoS channel by placing ahigher priority on higher QoS level traffic. In some embodiments, thisQoS priority is implemented in a number of ways, including routing thehigher priority QoS traffic into first priority in the downstream and/orupstream traffic queues. Upstream traffic queuing is performed directlyin some embodiments by transmitting guaranteed bit rate traffic first athigher available throttling rates, differentiated QoS traffic secondwith a controlled throttling rate, best effort traffic third withpossibly lower controlled throttled rates, and/or background trafficfourth when/if bandwidth not needed by the higher levels of QoS trafficand at lower controlled throttling rates. For example, downstreamtraffic can be handled by queuing traffic and delaying or preventing TCPacknowledgements to be returned for the lower levels of QoS priority,while immediately passing the traffic and TCP acknowledgements forhigher levels of QoS priority. The device link portion of the QoSchannel is thus provisioned by assigning policies for the queuingpriority, delay, throttle rate, and TCP acknowledgement return rate fordevice traffic in accordance with the bandwidth that is available at anypoint in time for the device. In some embodiments, various deviceservice processor traffic control capabilities regulate or partiallyregulate QoS in accordance with a set of network policy instructions,including, in some embodiments, a service plan policy set.

In some embodiments the device service processor establishes multipleQoS channels through the device traffic path with each QoS channelhaving traffic control policies as described herein, with each QoSchannel policy set creating a different class of QoS. In someembodiments, employing this multiple QoS channel approach, QoS for agiven service activity is provided by routing the traffic for that QoSactivity to the appropriate QoS channel with the appropriate QoS policysettings. The routing to the appropriate QoS channel can be providedusing various techniques. For example, the routing can be provided byapplying a common service traffic control policy set to trafficassociated with all QoS service activities that require or request theQoS provided by the common service traffic control policy set. Theapplication of the service traffic control policy set can beaccomplished in a number of ways utilizing the embodiments described forthe policy implementation agent and the policy control agent describedherein. In such embodiments, the problem of assigning a QoS channel to anumber of QoS service activities is reduced to applying a pre-determinedset of service traffic control policies to each of the QoS serviceactivities, with each pre-determined set of service traffic controlpolicies representing a different QoS class. The device can then managethe overall QoS for all traffic based on the available traffic capacityand quality, the total aggregate traffic demand for each QoS trafficclass and the policy rules that determine how each traffic class isprovided with differential bit rate and traffic quality as compared tothe other traffic classes for a given level of available trafficcapacity and quality.

Based on the aggregate demand for each traffic QoS class, and thetraffic capacity and quality level available to the device, the serviceprocessor can adjust the total available bit rate or percentage ofavailable traffic capacity for each QoS class. For example, in someembodiments, the aggregate demand for the real time interactive trafficcontrol class (e.g. services, such as VOIP, emergency communicationservices or high performance real time competitive gaming) can bedetermined, and the QoS routing function on the device (e.g., a QoSrouter agent/function) can first allocate enough constant bit ratetraffic capacity from the available traffic capacity to satisfy theseservices, with each QoS service activity that requires this QoS classbeing assigned to this QoS channel. As more QoS service activitiesrequire this traffic class, the capacity allocated to the QoS channelout of the available device capacity is increased, and when fewer QoSservice activities require this traffic class the capacity for this QoSchannel is released. In the event that the device does not have any moreavailable capacity with a guaranteed bit rate QoS level, then additionalQoS service activities that desire, require or request this QoS levelwill not be provided this QoS level, and instead will either be providedwith a lower QoS level or will not be allowed to connect to the accessnetwork. In some embodiments, there can be a hierarchy among thepossible QoS service activities so that if there is no more capacityavailable at a given service QoS level, then the available capacity forthat QoS class is provided to the service activities requiring that QoSfrom highest priority to lowest, until the available QoS class capacityis consumed, and then one or more QoS service activities that are toolow on the priority list to obtain service with that QoS class areeither bumped to a lower QoS class or are denied access. In someembodiments, once the required capacity to satisfy the real timeconstant rate traffic needs is satisfied, the remaining capacityavailable to the device is then divided among the other QoS channelclasses in accordance with a priority policy, with the priority policybeing based on the relative priority of each service class, the relativepriority of each QoS service activity, or a combination of the relativepriority of each QoS service class and each QoS service activity. Forexample, these relative priority policies can vary from device to devicebased on service plan selection, device type, user standing, user group,device location, device network connection, type of network, time ofday, network busy state, and/or other criteria/measures.

In some embodiments, a QoS link is established between the device and anaccess network equipment element. For example, such equipment elementembodiments can include a 2G/3G/4G wireless base station, a wirelessaccess point, a cable network head end, a DSL network DSLAM, a fibernetwork device traffic aggregator, a satellite network device trafficaggregator, a frame relay aggregation node, an ATM aggregation node,and/or other network equipment. In some embodiments, a logicalcommunication channel is created between the device and the networkequipment element, with the logical communication channel supporting agiven level of QoS or QoS class traffic policy set. For example, thelogical channel can include a RAB formed between a 2G/3G/4G base stationand a wireless end point device. The RAB can be formed by controllingthe media access control (MAC) parameters of the base station radiochannel so that a given level of QoS class policies can be implemented.For example, the RAB can support constant bit rate, low latencycommunication traffic for guaranteed bit rate real time traffic, or adifferentiated high priority access channel for streaming traffic, or abest effort random access channel for best effort traffic, or anavailable unused capacity traffic for background traffic. The QoSchannel link created in this manner can be dedicated to a single device,or shared with a subset of devices, or available to all devices. The QoSchannel link created in this manner can be used by the device to supporta single QoS activity as described herein, or a group of QoS activitiesas described herein. It will now be apparent to one of ordinary skill inthe art that similar settings for cable head end and cable modem MAC canyield similar QoS classes for QoS links for the cable modem case andthat similar techniques can be applied for a wireless access point or asatellite system MAC to achieve similar QoS classes for QoS links. Itwill also now be apparent to one of ordinary skill in the art that bycreating multiple logical channels in the device link, and/or adjustingthe available access network capacity and quality for each logicaldevice communication channel in the DSLAM or fiber aggregator, similarQoS class QoS links can be established for the DSL and fiberdistribution network cases.

In some embodiments the device service processor serves to route QoSservice activities to the appropriate logical communication channelestablished for the desired QoS class supported by a QoS link betweenthe device and the access network equipment element. In someembodiments, the device service processor elements (e.g., the policyimplementation agent and/or the policy control agent) can be used insome embodiments to assign the same QoS traffic control policies to oneor more QoS service activities that require the same QoS level. In asimilar manner, in some embodiments, the device service processorelements can be used to assign or route service activity traffic for agiven QoS class to the correct logical communication channel between thedevice and the access network element (e.g., a 2G/3G/4G base station)that supports the traffic control policies for the desired QoS class.For example, a QoS service link that supports guaranteed bit rate andlatency can be established with one or more RABs from a base station tothe device, and a second QoS service link can be established thatsupports differentiated preferred access for streaming content using oneor more differentiated access RABs, and a third best effort RAB can beused to support best effort traffic. Each of the required RABs is firstrequested and then provisioned as described herein based on theaggregate required capacity and quality for one or more QoS serviceactivities that require or desire the specific QoS service classassociated with the RAB logical channel policy parameters. Once the setof logical QoS channels is thus established, the service processor(e.g., QoS router agent/function) routes the traffic associated witheach QoS service activity to the appropriate RAB. In some embodiments,the service processor can detect increases or decreases in aggregate QoSclass demand for each QoS class as QoS activities are initiated orterminated for that QoS class, and the service processor can communicatethe required increases or decreases in the RAB assignments required tosupport that logical QoS channel.

In some embodiments, the access QoS link is established by directcommunication from the device in which the device requests the QoSchannel or link from the access network equipment element, or the devicerequests the QoS channel or link from an intermediate networking device,such as a service controller (e.g., or a readily substituted device withsimilar features, such as a home agent, an HLR, a mobile switchingcenter, a base station, an access gateway, a AAA system, or a billingsystem). In some embodiments, the device service processor bases the QoSchannel or link request on an association the device performs to match aQoS service activity with a desired or required QoS class or QoS trafficcontrol policy set. For example, this association of QoS class or QoStraffic control policy set with QoS service activity can be determinedby a predefined policy mapping that is stored on the device and used bythe service processor. In some embodiments, this policy mapping store ispopulated and/or updated by a service controller (e.g., or similarfunction as described herein). In some embodiments, the mapping isdetermined by a service controller (e.g., or similar function asdescribed herein) based on a report from the device of the QoS serviceactivity that needs the QoS channel or link.

In some embodiments, the required or desired QoS level for one or moreQoS service activities is determined by a set of QoS service trafficcontrol policies that are pre-assigned to various QoS serviceactivities. For example, a given application can be pre-assigned a QoSclass. As another example, a web service destination such as a VOIPservice site can be assigned a QoS class. As another example, a givenapplication can have one QoS assignment level for general Internettraffic but have a QoS assignment for real-time gaming traffic. Asanother example, a real-time broadcasting website can have a best effortQoS level assigned to programming information and general browsing andhave a differentiated streaming QoS level for broadcast traffic content.In some embodiments, detection of QoS need or QoS assignment request fora given activity can be assigned by a device service processor accordingto a predefined QoS policy rules table (e.g., QoS activity table), orcan be determined by a service controller based on information reportedby the device, or can be requested by an application through a QoSapplication interface (e.g., QoS API), or can be determined by thenature of incoming traffic.

In embodiments, in which both end points in the QoS channel participatein establishing an end to end QoS channel, the required QoS level isdetermined and/or communicated by the originating end point. In someembodiments, the required QoS level is determined and/or communicated bythe receiving end point. In some embodiments the QoS level is determinedand/or communicated by the originating end point service controller(e.g., or the access network element (such as a base station), the HLR,home agent, mobile switching center, AAA, gateway, or other networkelement/function). In some embodiments, the QoS level is determinedand/or communicated by the receiving end point service controller (e.g.,or alternatively the access network element (such as a base station),the HLR, home agent, mobile switching center, AAA, gateway, or othernetwork element/function). In some embodiments, the receiving end pointservice controller (e.g., or the access network element (such as a basestation), the HLR, home agent, mobile switching center, AAA, gateway orother network function) and the originating end point service controller(e.g., or other similar function) communicate with one another tocoordinate establishment of the QoS channel between the end points.

In some embodiments, the near end or originating end device serviceprocessor contacts the far end or terminating device service processorto initiate a QoS channel. In some embodiments, the initiation of theQoS channel from the near end or originating device is performedautomatically by the far end device when its service processor detectsthat a given level of QoS is needed for the communication between thetwo devices. In some embodiments, the near end or originating deviceservice processor detects the need for a QoS channel to the far end orterminating device and contacts a central network resources, such as theservice controller (e.g., or other equipment element with similarfunction for this purpose), and the service controller provisions thefar end of the QoS channel, either by communicating directly with thefar end device or by communicating with the far end device's servicecontroller (e.g., or other equipment element with similar function forthis purpose). In some embodiments, in which the far end device servicecontroller is contacted to assist in provisioning the QoS channel, thereis a look up function to determine the address of the far end servicecontroller based on a look up index formed from some aspect of the farend device credentials (e.g., phone number, SIM ID, MEID, IMSI, IPaddress, user name, and/or other device credentials).

In some embodiments, the mapping of QoS service activity to the desiredlevel of QoS class or QoS traffic control policies is determined byproviding a QoS API in the device service processor that applicationsuse to request a QoS class or QoS channel connection. In someembodiments, an API is provided so that application developers cancreate application software that uses the standard interface commands torequest and set up QoS channels. In some embodiments, the API does oneor more of the following: accepts QoS requests from an application,formats the QoS channel request into a protocol appropriate fortransmission to network equipment responsible for assessing QoS channelavailability (e.g., including possibly the device traffic controlsystem), coordinates with other network elements (e.g., includingpossibly the device traffic control system) to reserve a QoS channel,coordinates with other network elements (e.g., including possibly thedevice traffic control system) to provision a QoS channel, informs theapplication that the desired QoS channel can be created or not, and/orcoordinates with other network elements (e.g., including possibly thedevice traffic control system) to connect the application with thedesired QoS channel class. In some embodiments, the QoS API accepts theapplication QoS request and communicates and possibly coordinates withone or more QoS network equipment elements, such as a base station,cable head end or access point. In some embodiments, the QoS API acceptsthe QoS request from the application and communicate and possiblycoordinates with an intermediate network element, such as a serviceprocessor (e.g., or other similar function as described herein). In someembodiments the QoS API assesses the QoS service plan standing for thedevice or user before sending QoS channel requests to other networkelements, and only initiates the QoS request sequence if requiredservice plan authorization is in place. In this manner, the potentiallycomplex process of establishing a QoS channel with all the specificequipment communication protocols that typically need to be supported toassess QoS channel availability and provision the QoS channel aresimplified into a limited set of API commands that are easy for anapplication development community to learn about and use for QoSdifferentiated services and applications.

In some embodiments, local traffic control on the device serviceprocessor is combined with traffic control in the link between thedevice and the access network equipment element. In this manner, boththe device traffic control path QoS link and the device to accessnetwork element QoS link can be coordinated for best device QoSperformance results given the available capacity and quality of theaccess network traffic for the device. In some embodiments, the policiesfor how the device manages local traffic control, establishes accessnetwork element logical channels (e.g., RABs) and routes traffic to andfrom the access network element logical channels is all determined bypredefined policy rules loaded onto the device by the service controller(or other equivalent network element). In some embodiments, thesepolicies are determined in the service controller itself.

In some embodiments, a QoS user interface (e.g., QoS UI) is presented tothe Device user. In some embodiments, the QoS UI notifies the user whatlevel of QoS services the device is authorized to receive based on theservice plan selection. In some embodiments, the QoS UI notifies theuser what level of QoS services are available on the present network thedevice is connected to at the present time. In some embodiments, the QoSUI notifies the user when a level of QoS service that is higher thanthat authorized by the user service plan is required or desirable for agiven service activity that the device has initiated. In someembodiments, the QoS UI provides the user with a set of one or moreupgrade options to upgrade the service plan to include a higher level ofQoS for one or more service activities. In some embodiments, the QoS UIprovides the user with an opportunity to specify what level of QoS theuser would like to employ for one or more service usage activities. Insome embodiments, the QoS UI allows the user to specify a service plansetting that provides differentiated QoS during times when the networkis busy. In some embodiments, the QoS UI allows the user to purchase oneor more grades of service QoS with either a post-pay for a pre-definedservice period and one or more pre-defined service usage limits by QoSclass, a pre-pay for one or more pre-defined service usage limits by QoSclass, or another payment system for differentiated QoS services. Insome embodiments, the QoS UI provides the user with an opportunity toQoS enable or pay for QoS services for a connection that is initiated byan incoming connection to the device.

In some embodiments, QoS for DAS techniques include verifying that thedevice is properly implementing the QoS traffic control policies, forexample, in accordance with a service plan. This ensures that errors,hacking, user device software settings manipulations, or other malwareevents do not result in inappropriate levels of QoS for a given deviceor group of devices. Accordingly, in some embodiments, the trafficcontrol and QoS verification techniques described herein are employed toverify that the proper level of QoS is applied for a given service usageactivity in accordance with a QoS priority policy. For example,verification of QoS channel request policy rules behavior can beimplemented in a variety of ways including, as an example, monitoringdevice QoS channel requests and comparing the level of QoS requestedwith the level of QoS the device is authorized to receive in the serviceplan in effect for the device. Verification of proper QoS channel usagebehavior by a device can be implemented in a variety of ways including,for example, monitoring network based reports of QoS service usage andcomparing the network based reports against the service policy rulesthat should be in effect given the device service plan. Verification ofproper device traffic control to implement a QoS service policy that isin effect can be accomplished in a variety of ways by verifying that theappropriate traffic control policy rules are being properly implementedas described herein.

In some embodiments, the QoS router prioritizes traffic on the device.In some embodiments, the QoS router connects the QoS enabled session tothe RAB that has the proper QoS level. In some embodiments, one sessionis routed to the RAB. In some embodiments, more than one session can berouted to an RAB. In some embodiments, multiple RABs providing multipleQoS levels are created to the device, and the QoS router routes eachservice activity to the RAB dictated by the QoS policy rules in effecton the device.

In some embodiments, the network collects service usage charges fordifferent QoS classes. In some embodiments, there is differentiatedservice charging for the different classes of QoS service usage. As anexample, since guaranteed bit rate traffic consumes network resourceswhether the traffic capacity is used or not, there can be a time elementinvolved in the charging calculations. As a more detailed example,guaranteed bit rate services can be charged by the total bandwidthprovisioned to the device at a given time multiplied by the amount oftime that that bandwidth is made available. In some embodiments,differentiated access traffic that has higher QoS than best efforttraffic but is not guaranteed bit rate can be charged at a higher ratethan best effort traffic but lower than guaranteed bit rate. In someembodiments, such traffic can be charged based on the time the QoSchannel is made available and the total amount of data transmitted overthe channel, or can only be based on the total amount of datatransmitted over the channel. Best effort traffic is charged in someembodiments based only on the total amount of data used, with the datacharges being less than differentiated streaming access services.Background data services in some embodiments are charged at the lowestrate, possibly with only certain times of the day or periods of lownetwork traffic demand being available for such services, and with theservice being based on total data transmitted. In some embodiments, allQoS service levels can be charged based on a fixed price for a fixedcharging period, possibly with a service usage cap with additionalcharges if the service cap is exceeded. In such fixed price scenarioembodiments, the price charged is again higher for higher levels of QoS.

In some embodiments, the network equipment (e.g., access networkelement, gateways, AAA, service usage storage systems, home agent, HLR,mobile data center, and/or billing systems) record and report serviceusage for one or more of the QoS service classes used by the device. Insome embodiments, the device service processor records and reportsservice usage for one or more of the QoS service classes used by thedevice and reports the QoS service class usage to the service controller(e.g., or another substitute network element). In some embodiments, inwhich the device is recording reporting usage for one or more QoSservice classes, it is important to verify the device service usagereports to ensure that the device usage reports are not distorted,tampered with, and/or otherwise in error. In some embodiments, verifyingservice usage reports against service usage that should be occurringgiven the service control policies in place on the device, serviceprocessor agent functional operation verification, test service usageevents, agent query response sequences, device service processorsoftware protection techniques, device service processor softwareenvironment checks, and several other techniques are provides asdescribed herein. For example, using one or more of these verificationtechniques can provide a verifiable device assisted QoS service usagecharging system.

In some embodiments, device assisted traffic control is provided formanaging network congestion as follows. For example, when a given basestation or group of base stations experience traffic demand that is highrelative to the available capacity and/or service quality that can beprovided, and such a condition is detected by means of network busystate assessment as described below, then a service controller (e.g., oranother interchangeable network function) can issue traffic controlthrottling policies to the devices in accordance with a measure of theexcess traffic demand the one or more base stations is experiencing. Forexample, the device service processors connected to an overly busy basestation can be instructed to reduce the traffic control priority for oneor more classes of QoS traffic, reducing the queuing priority,throttling rate, delay and/or access allowance for some or all of one ormore classes of traffic. As another example, background downloadprocesses, such as software updates can be turned off completely orthrottled back significantly. As another example, best effort trafficsuch as Internet browsing can be throttled or reduced for a group ofdevices connected to base stations experiencing excess traffic demand.As another example, a policy can be implemented on the devices connectedto busy base stations in which the device is allowed to browse orconduct other best effort service activities at a relatively highthrottling rate for a period of time, but if the device uses more than acertain amount of service (e.g., total data downloaded and/or uploaded)in a certain period of time then the device may be traffic controlledaccording to an adaptive throttling policy as described herein. In someembodiments, higher QoS level traffic cannot be throttled in suchcircumstances, such as VOIP traffic where real time guaranteed bit rateis important to meet user service needs or expectations, while lowerpriority traffic such as interactive browsing and/or background downloadare throttled and/or blocked. In some embodiments, the QoS availabilityassessment processes described herein are adjusted so that higher QoSchannels are not provided and provisioned in times or locations in whicha given base station or group of base stations experience excess demandor demand above a given threshold.

In some embodiments, users or devices that have service plans withhigher QoS levels, or service plans with higher priority during busynetwork periods have different traffic control policies applied to themthat result in a higher level of traffic performance and/or a higherlevel of QoS service availability. For example, emergency serviceworkers can be given higher traffic control access policies that resultin differentiated services during peak busy times on the network or aportion of the network. In some embodiments, users can obtain a premiumservice plan for differentiated access during peak busy time periods ormay use higher levels of QoS service settings and/or service plans toachieve differentiated service during peak busy periods. As anotherexample, services that demand high levels of QoS classes, such as realtime voice services, instant messaging, push to talk, differentiatedvideo streaming, and/or interactive gaming, are not traffic controlledto the same extent that other lower priority services or lower classservice plans are traffic controlled during peak busy times. Forexample, this type of service differentiation can also be applied basedon device type, user group, user standing, user reward zone points,and/or other criteria/measures as similarly described herein.

In some embodiments, the decision to reduce the access traffic controlsettings as described above is made by the device service processorbased on the device's assessment of the network capacity, which can bedetermined using various techniques as described herein. In someembodiments, the decision to reduce the access traffic control settingsas described above is made by a service controller (e.g., or otherinterchangeable network equipment element or elements as describedherein) connected to the device that provides instructions to the deviceto adjust the access policy settings. For example, the servicecontroller can obtain the network capacity information from accessequipment elements, from device reports of traffic capacity and/orquality as described herein, or from reports on traffic capacity and/orquality obtained from dedicated devices used for the purpose ofassessing network capacity. In some embodiments, the decision to reducethe access traffic control settings as described above is based on thetime of day or day of week or both to accommodate cyclical patterns innetwork capacity and traffic demand.

In some embodiments, a service controller (e.g., or anotherinterchangeable network equipment element or elements, as describedherein) assesses network busy state and then controls device trafficdemand by reducing the offered capacity for one or more service classessupported by the access network equipment elements such as a wirelessbase station. In such embodiments, the service controller (e.g., orsimilar function) gathers the network capacity information with one ofthe techniques described herein and instructs one or more of the accessnetwork equipment elements to reduce the offered capacity for one ormore levels of service QoS, to one or more of the devices connected tothe access network equipment elements. For example, the determination ofwhich devices to throttle back can be made based on an equal throttlingof all devices of a given service plan status, or based on the devicetraffic usage patterns in the recent past as described herein, or basedon a combination of service plan status and recent traffic usagepatterns.

In some embodiments, the device is enabled with ambient services thathave differentiated QoS services as part of the ambient serviceoffering. For example, this can be accomplished using the pre-assignedQoS policies for a given service activity set within the ambientservice, or using an ambient service application that requests QoSthrough the QoS API. Other embodiments for providing QoS differentiatedservice activities within ambient service offerings will now be apparentto one of ordinary skill in the art.

In some embodiments, a QoS service control policy is adapted as afunction of the type of network the device is connected to. For example,the QoS traffic control policies and/or the QoS service chargingpolicies can be different when the device is connected to a wirelessnetwork (e.g., a 3G/4G network where there is in general less availableQoS enabled traffic capacity) than when the device is connected to awired network (e.g., a cable or DSL network where there is in general ahigher level of QoS capacity available). In such embodiments, the deviceservice processor and the service controller can coordinate to adapt theQoS service control policies and/or the QoS service charging policies tobe different depending on which network the device is connected to.Similarly, the device QoS service control policy and/or QoS servicecharging policy can also be adapted based on whether the device isconnected to a home wireless network or a roaming wireless network.

In some embodiments, various of the QoS related techniques describedherein are performed on the device using DAS techniques and/or on theservice controller in secure communication with a verified serviceprocessor executed on the device using DAS techniques. In someembodiments, various of the QoS related techniques described herein areperformed by/in coordination/communication with one or more intermediatenetwork elements/functions for assisting in various QoS functions.

FIG. 1 illustrates a functional diagram of a network architecture forproviding quality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments. In some embodiments, QoS for DAStechniques described herein are implemented using the networkarchitecture shown in FIG. 1.

As shown, FIG. 1 includes a 4G/3G/2G wireless network operated by, forexample, a central provider. As shown, various wireless devices 100 arein communication with base stations 125 for wireless networkcommunication with the wireless network (e.g., via a firewall 124), andother devices 100 are in communication with Wi-Fi Access Points (APs) orMesh 702 for wireless communication to Wi-Fi Access CPE 704 incommunication with central provider access network 109. In someembodiments, one or more of the devices 100 are in communication withother network element/equipment that provides an access point, such as acable network head end, a DSL network DSLAM, a fiber network aggregationnode, and/or a satellite network aggregation node. In some embodiments,each of the wireless devices 100 includes a service processor 115 (asshown) (e.g., executed on a processor of the wireless device 100), andeach service processor connects through a secure control plane link to aservice controller 122 (e.g., using encrypted communications).

In some embodiments, service usage information includes network basedservice usage information (e.g., network based service usage measures orCDRs, which can, for example, be generated by service usage measurementapparatus in the network equipment), which is obtained from one or morenetwork elements (e.g., BTS/BSCs 125, RAN Gateways (not shown),Transport Gateways (not shown), Mobile Wireless Center/HLRs 132, AAA121, Service Usage History/CDR Aggregation, Mediation, Feed 118, orother network equipment). In some embodiments, service usage informationincludes micro-CDRs. In some embodiments, micro-CDRs are used for CDRmediation or reconciliation that provides for service usage accountingon any device activity that is desired. In some embodiments, each deviceactivity that is desired to be associated with a billing event isassigned a micro-CDR transaction code, and the service processor 115 isprogrammed to account for that activity associated with that transactioncode. In some embodiments, the service processor 115 periodicallyreports (e.g., during each heartbeat or based on any other periodic,push, and/or pull communication technique(s)) micro-CDR usage measuresto, for example, the service controller 122 or some other networkelement. In some embodiments, the service controller 122 reformats theheartbeat micro-CDR usage information into a valid CDR format (e.g., aCDR format that is used and can be processed by an SGSN or GGSN or othernetwork elements/equipment used/authorized for generating or processingCDRs) and then transmits it to a network element/function for CDRmediation (e.g., CDR Storage, Aggregation, Mediation, Feed 118).

In some embodiments, CDR mediation is used to account for the micro-CDRservice usage information by depositing it into an appropriate serviceusage account and deducting it from the user device bulk service usageaccount. For example, this technique provides for a flexible serviceusage billing solution that uses pre-existing solutions,infrastructures, and/or techniques for CDR mediation and billing. Forexample, the billing system (e.g., billing system 123 or billinginterface 127) processes the mediated CDR feed from CDR mediation,applies the appropriate account billing codes to the aggregatedmicro-CDR information that was generated by the device, and thengenerates billing events in a manner that does not require changes tothe existing billing systems (e.g., using new transaction codes to labelthe new device assisted billing capabilities). In some embodiments,network provisioning system 160 provisions various networkelements/functions for authorization in the network, such as toauthorize certain network elements/functions (e.g., CDR storage,aggregation, mediation, feed 118 or other network elements/functions)for providing micro-CDRs, reformatted micro-CDRs, and/or aggregated orreconciled CDRs.

As shown in FIG. 1, a CDR storage, aggregation, mediation, feed 118 isprovided. In some embodiments, the CDR storage, aggregation, mediation,feed 118 receives, stores, aggregates and mediates micro-CDRs receivedfrom mobile devices 100. In some embodiments, the CDR storage,aggregation, mediation, feed 118 also provides a settlement platformusing the mediated micro-CDRs, as described herein. In some embodiments,another network element provides the settlement platform usingaggregated and/or mediated micro-CDRs (e.g., central billing interface127 and/or another network element/function).

In some embodiments, various techniques for partitioning of devicegroups are used for partitioning the mobile devices 100 (e.g.,allocating a subset of mobile devices 100 for a distributor, an OEM, aMVNO, and/or another partner or entity). As shown in FIG. 1, a MVNO corenetwork 210 includes a MVNO CDR storage, aggregation, mediation, feed118, a MVNO billing interface 122, and a MVNO billing system 123 (andother network elements as shown in FIG. 1). In some embodiments, theMVNO CDR storage, aggregation, mediation, feed 118 receives, stores,aggregates and mediates micro-CDRs received from mobile devices 100(e.g., MVNO group partitioned devices).

Those of ordinary skill in the art will appreciate that various othernetwork architectures can be used for providing device group partitionsand a settlement platform, and FIG. 1 is illustrative of just one suchexample network architecture for which device group partitions andsettlement platform techniques described herein can be provided.

In some embodiments, CDR storage, aggregation, mediation, feed 118(e.g., service usage 118, including a billing aggregation data store andrules engine) is a functional descriptor for, in some embodiments, adevice/network level service usage information collection, aggregation,mediation, and reporting function located in one or more of thenetworking equipment apparatus/systems attached to one or more of thesub-networks shown in FIG. 1 (e.g., central provider access network 109and/or central provider core network 110), which is in communicationwith the service controller 122 and a central billing interface 127. Asshown in FIG. 1, service usage 118 provides a function in communicationwith the central provider core network 110. In some embodiments, the CDRstorage, aggregation, mediation, feed 118 function is located elsewherein the network or partially located in elsewhere or integrated with/aspart of other network elements. In some embodiments, CDR storage,aggregation, mediation, feed 118 functionality is located or partiallylocated in the AAA server 121 and/or the mobile wireless center/HomeLocation Register(HLR) 132 (as shown, in communication with a DNS/DHCPserver 126). In some embodiments, service usage 118 functionality islocated or partially located in the base station, base stationcontroller and/or base station aggregator, collectively referred to asbase station 125 in FIG. 1. In some embodiments, CDR storage,aggregation, mediation, feed 118 functionality is located or partiallylocated in a networking component in the central provider access network109, a networking component in the core network 110, the central billingsystem 123, the central billing interface 127, and/or in another networkcomponent or function. This discussion on the possible locations for thenetwork based and device based service usage information collection,aggregation, mediation, and reporting function (e.g., CDR storage,aggregation, mediation, feed 118) can be easily generalized as describedherein and as shown in the other figures and embodiments describedherein by one of ordinary skill in the art. Also as shown in FIG. 1, theservice controller 122 is in communication with the central billinginterface 127 e.g., sometimes referred to as the external billingmanagement interface or billing communication interface), which is incommunication with the central billing system 123. As shown in FIG. 1,an order management 180 and subscriber management 182 are also incommunication with the central provider core network 110 forfacilitating order and subscriber management of services for the devices100 in accordance with some embodiments.

In some embodiments, a service processor download 170 is provided, whichprovides for periodical downloads/updates of service processors (e.g.,service processor 115). In some embodiments, verification techniquesinclude periodically updating, replacing, and/or updating an obfuscatedversion of the service processor, or performing any of these techniquesin response to an indication of a potential compromise or tampering ofany service processor functionality and/or QoS functionality executed onor implemented on the device 100.

In some embodiments, the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)provides a device/network level service usage information collection,aggregation, mediation, and reporting function. In some embodiments, theCDR storage, aggregation, mediation, feed 118 (and/or other networkelements or combinations of network elements) collects devicegenerated/assisted service usage information (e.g., micro-CDRs) for oneor more devices on the wireless network (e.g., devices 100); andprovides the device generated service usage information in a syntax anda communication protocol that can be used by the wireless network toaugment or replace network generated usage information for the one ormore devices on the wireless network. In some embodiments, the syntax isa charging data record (CDR), and the communication protocol is selectedfrom one or more of the following: 3GPP, 3GPP2, or other communicationprotocols. In some embodiments, as described herein, the CDR storage,aggregation, mediation, feed 118 collects/receives micro-CDRs for one ormore devices on the wireless network (e.g., devices 100). In someembodiments, the CDR storage, aggregation, mediation, feed 118 (and/orother network elements or combinations of network elements) includes aservice usage data store (e.g., a billing aggregator) and a rules enginefor aggregating the collected device generated service usageinformation. In some embodiments, the network device is a CDR feedaggregator, and the CDR storage, aggregation, mediation, feed 118 (e.g.,other network elements and/or various combinations of network elements)also aggregates (network based) CDRs and/or micro-CDRs for the one ormore devices on the wireless network; applies a set of rules to theaggregated CDRs and/or micro-CDRs using a rules engine (e.g., bill byaccount, transactional billing, revenue sharing model, and/or any otherbilling or other rules for service usage information collection,aggregation, mediation, and reporting), and communicates a new set ofCDRs for the one or more devices on the wireless network to a billinginterface or a billing system (e.g., providing a CDR with a billingoffset by account/service). In some embodiments, a revenue sharingplatform is provided using various techniques described herein.

In some embodiments, the CDR storage, aggregation, mediation, feed 118(e.g., or other network elements and/or various combinations of networkelements) communicates a new set of CDRs (e.g., aggregated and mediatedCDRs and/or micro-CDRs that are then translated into standard CDRs for agiven wireless network) for the one or more devices on the wirelessnetwork to a billing interface (e.g., central billing interface 127) ora billing system (e.g., central billing system 123). In someembodiments, the CDR storage, aggregation, mediation, feed 118 (e.g., orother network elements and/or various combinations of network elements)communicates with a service controller (e.g., service controller 122) tocollect the device generated service usage information (e.g.,micro-CDRs) for the one or more devices on the wireless network. In someembodiments, the CDR storage, aggregation, mediation, feed 118 (and/orother network elements or combinations of network elements) communicateswith a service controller, in which the service controller is incommunication with a billing interface or a billing system. In someembodiments, the CDR storage, aggregation, mediation, feed 118 (e.g., orother network elements and/or combinations of network elements)communicates the device generated service usage information to a billinginterface or a billing system. In some embodiments, the CDR storage,aggregation, mediation, feed 118 (e.g., other network elements and/orvarious combinations of network elements) communicates with a transportgateway and/or a Radio Access Network (RAN) gateway to collect thenetwork generated/based service usage information for the one or moredevices on the wireless network. In some embodiments, the servicecontroller 122 communicates the device assisted service usageinformation (e.g., micro-CDRs) to the CDR storage, aggregation,mediation, feed 118 (e.g., or other network elements and/or variouscombinations of network elements).

In some embodiments, the CDR storage, aggregation, mediation, feed 118(and/or other network elements or combinations of network elements)performs rules for performing a bill by account aggregation andmediation function. In some embodiments, the CDR storage, aggregation,mediation, feed 118 (and/or other network elements or combinations ofnetwork elements) performs rules for performing a service billingfunction, as described herein, and/or for performing aservice/transactional revenue sharing function, as described herein. Insome embodiments, the service controller 122 in communication with theCDR storage, aggregation, mediation, feed 118 (and/or other networkelements or combinations of network elements) performs a rules enginefor aggregating and mediating the device assisted service usageinformation (e.g., micro-CDRs). In some embodiments, a rules enginedevice in communication with the CDR storage, aggregation, mediation,feed 118 (and/or other network elements or combinations of networkelements) performs a rules engine for aggregating and mediating thedevice assisted service usage information.

In some embodiments, the rules engine is included in (e.g., integratedwith/part of) the CDR storage, aggregation, mediation, feed 118. In someembodiments, the rules engine and associated functions, as describedherein, is a separate function/device. In some embodiments, the servicecontroller 122 performs some or all of these rules engine basedfunctions, as described herein, and communicates with the centralbilling interface 127. In some embodiments, the service controller 122performs some or all of these rules engine based functions, as describedherein, and communicates with the central billing system 123.

In some embodiments, a settlement platform service is provided. Forexample, micro-CDRs can be aggregated and mediated to associate serviceusage for one or more services used by a communications device (e.g., auser of the communications device). A rules engine or another functioncan determine a revenue share allocation for the service usage for aparticular service to determine the settlement for such service usagefor the revenue sharing allocation/model and to distribute accountingand settlement information to one or more of carriers, distributionpartners, MVNOs, wholesale partners, and/or other partners or entities.In some embodiments, the service is a transactional service.

In some embodiments, duplicate CDRs are sent from the network equipmentto the billing system 123 that is used for generating service billing.In some embodiments, duplicate CDRs are filtered to send only thoseCDRs/records for devices controlled by the service controller and/orservice processor (e.g., managed devices). For example, this approachcan provide for the same level of reporting, lower level of reporting,and/or higher level of reporting as compared to the reporting requiredby the central billing system 123.

In some embodiments, a bill-by-account billing offset is provided. Forexample, bill-by-account billing offset information can be informed tothe central billing system 123 by providing a CDR aggregator feed thataggregates the device assisted service usage data feed to provide a newset of CDRs for the managed devices to the central billing interface 127and/or the central billing system 123. In some embodiments, transactionbilling is provided using similar techniques. For example, transactionbilling log information can be provided to the central billing interface127 and/or the central billing system 123.

In some embodiments, the rules engine (e.g., performed by the serviceusage 118 or another network element, as described herein) provides abill-by-account billing offset. For example, device assisted serviceusage information (e.g., micro-CDRs) includes a transaction type fieldor transaction code (e.g., indicating a type of service for theassociated service usage information). For example, the rules engine canapply a rule or a set of rules based on the identified serviceassociated with the device generated service usage information todetermine a bill-by-account billing offset (e.g., a new CDR can begenerated to provide the determined bill-by-account billing offset). Insome examples, the determined bill-by-account billing offset can beprovided as a credit to the user's service usage account (e.g., a newCDR can be generated with a negative offset for the user's service usageaccount, such as for network chatter service usage, or transactionalservice usage, or for any other purposes based on one or more rulesperformed by the rules engine).

As another example, for a transactional service, a first new CDR can begenerated with a negative offset for the user's service usage accountfor that transactional service related usage, and a second new CDR canbe generated with a positive service usage value to charge that sameservice usage to the transactional service provider (e.g., Amazon, eBay,or another transactional service provider). In some embodiments, theservice controller 122 generates these two new CDRs, and the serviceusage 118 stores, aggregates, and communicates these two new CDRs to thecentral billing interface 127. In some embodiments, the servicecontroller 122 generates these two new CDRs, and the service usage 118stores, aggregates, and communicates these two new CDRs to the centralbilling interface 127, in which the central billing interface 127applies rules (e.g., performs the rules engine for determining thebill-by-account billing offset).

In some embodiments, the service controller 122 sends the devicegenerated CDRs to the rules engine (e.g., a service usage data store andrules engine, such as CDR storage, aggregation, mediation, feed 118),and the rules engine applies one or more rules, such as those describedherein and/or any other billing/service usage related rules as would beapparent to one of ordinary skill in the art. In some embodiments, theservice controller 122 generates CDRs similar to other network elements,and the rules (e.g., bill-by-account) are performed in the centralbilling interface 127. For example, for the service controller 122 togenerate CDRs similar to other network elements, in some embodiments,the service controller 122 is provisioned on the wireless network (e.g.,by network provision system 160) and behaves substantially similar toother CDR generators on the network).

In some embodiments, the service controller 122 is provisioned as a newtype of networking function that is recognized as a valid, authorized,and secure source for CDRs by the other necessary elements in thenetwork (e.g., CDR storage, aggregation, mediation, feed 118). In someembodiments, if the necessary network apparatus only recognize CDRs fromcertain types of networking equipment (e.g. a RAN gateway or transportgateway), then the service controller 122 provides authenticationcredentials to the other networking equipment that indicate that it isone of the approved types of equipment for providing CDRs. In someembodiments, the link between the service controller 122 and thenecessary CDR aggregation and mediation equipment is secured,authenticated, encrypted, and/or signed.

In some embodiments, the CDR storage, aggregation, mediation, feed 118discards the network based service usage information (e.g., networkbased CDRs) received from one or more network elements. In theseembodiments, the service controller 122 provides the device assistedservice usage information (e.g., device based CDRs or micro-CDRs) to theCDR storage, aggregation, mediation, feed 118 (e.g., the CDR storage,aggregation, mediation, feed 118 can just provide a store, aggregate,and communication function(s), as it is not required to mediate networkbased CDRs and device assisted CDRs), and the device based service usageinformation is provided to the central billing interface 127 or thecentral billing system 123.

In some embodiments, the device based CDRs (e.g., micro-CDRs) and/or newCDRs generated based on execution of a rules engine as described hereinare provided only for devices that are managed and/or based on devicegroup, service plan, or any other criteria, categorization, and/orgrouping, such as based on ambient service or ambient service provideror transactional service or transactional service provider.

In some embodiments, QoS for DAS includes a service processor (e.g., anydevice assisted element/function) that facilitates coordination forand/or provisions wireless access/radio access bearers (e.g., RABs). Insome embodiments, the service processor determines whether a request forQoS is authorized (e.g., according to QoS service level, user standing,available local network capacity (e.g., as reported by other device(s)and/or network)). In some embodiments, device QoS capacity demandreports provide and/or augment network capacity demand reports.

In some embodiments, QoS for DAS includes a service controller (e.g.,any network device based service control element/function) thatfacilitates coordination for and/or provisions wireless access/radioaccess bearers (e.g., RABs) on a device (e.g., a communications device,such as a mobile wireless communications device and/or an intermediatenetworking device), on network, and/or on device plus network. In someembodiments, the service controller provides device QoS capacity demandreports to other network equipment/elements/functions, and then alsoprovisions the RAB channel based on various criteria and determinations.

In some embodiments, QoS for DAS provides for device assistedmonitoring, information, and/or functionality to facilitate QoS withoutand/or to assist network based monitoring, information, and/orfunctionality (e.g., Deep Packet Inspection (DPI) and/or provides suchmonitoring, information, and/or functionality that may not be availablevia network based monitoring, information, and/or functionality (e.g.,encrypted activities on the device may not be accessible by DPI or othernetwork based techniques). For example, QoS for DAS can assist in theQoS setup to facilitate the QoS setup and provide such information thatmay not otherwise be available using network based only techniques. Forexample, device assisted activity and/or service monitoring techniquescan assist in classifying the QoS for the monitored activity and/orservice using, for example, a QoS activity map (e.g., as describedherein or other similar techniques). For example, using such deviceassisted techniques eliminates and/or minimizes DPI or other networkbased techniques that can give rise to privacy concerns/issues, networkneutrality concerns/issues, and/or otherwise may not be able to providesimilar or equivalent granular service/activity monitoring, as discussedabove, and/or also off loads such processing from the network (e.g.,network elements/devices/functionality) to the communications devices(e.g., at least for such communications devices that can perform suchfunctions, based on their processing and/or memory capabilities, aswould be apparent to one of ordinary skill in the art). In someembodiments, QoS for DAS includes the service provider for providing aninitial authorization/clearance for a QoS request (e.g., using varioustechniques described herein), and the service controller determines ifthe QoS request should be authorized (e.g., based on various QoSauthorization/clearance/approval criteria (e.g., QoS activity mapsand/or QoS request rule) and/or network capacity, as described herein).In some embodiments, QoS for DAS includes the service provider forproviding a QoS request including a QoS class to the service controller,and the service controller determines if the QoS request should beauthorized, as described herein.

In some embodiments, QoS for DAS includes providing or facilitatingreports for base station (BTS) for network capacity (e.g., sector,channel, busy state information or network capacity usage/availability,and/or network capacity expected demand) based on, for example, one ormore of the following: monitored application usage on the communicationsdevice, monitored user activity on the communications device, locationof the communications, other available networks, and/or other monitoredor determined activity, service usage measure, and/or metric. In someembodiments, at or after execution of an application that is determinedto require network service usage (e.g., may require increased wirelessnetwork bandwidth, such as based on a service usage activity map), QoSfor DAS sends information to the network (e.g., a network controller orother network device element/function) that capacity demand isforthcoming for the communications device (e.g., potentially initiatinga provisioning of a QoS radio access bearer (RAB) or other type of RAB).

In some embodiments, network capacity (e.g., busy state information) iscollected from one or more communications devices in communication witha wireless network (e.g., network capacity/usage information measuredfrom each respective communications device's perspective is determinedand stored by the service processor on each respective communicationsdevice) and reported to the service controller, and the servicecontroller (e.g., or another network element/function) uses thisinformation to determine what resources are available for allocation tovarious levels of QoS (e.g., to respond to/facilitate various QoSrequests) and/or to workload balance across multiple base stationsand/or networks (e.g., cellular, Wi-Fi, and/or other wireless networks).

In some embodiments, the service processor executed on thecommunications device sends a QoS request (e.g., a wireless networkbearer channel reservation request or Radio Access Bearer (RAB) request)to the service controller. The service controller verifies the requestusing various verification techniques as described herein. In someembodiments, the service controller facilitates coordination of variousdevice QoS requests with one or more base stations (BTSs) incommunication with the communications device to provide for therequested QoS reservation to facilitate the new QoS session. In someembodiments, the service controller provides a QoS routing function by,for example, providing various QoS routing instructions to a deviceservice processor (e.g., aggregating, prioritizing, queuing,authorizing, allocating reservations/RABs, denying, re-routing (such asto other BTSs and/or other networks) and/or otherwise managing QoSrequests), in which the BTS may or may not be QoS aware. For example,QoS priority can be based on activity (e.g., service usage and/orapplication), service level, user standing, network capacity, time ofday, and/or QoS priority can be purchased on a transaction basis, asession basis, a pre-pay basis or a plan basis. As another example, QoSpriority can also vary by device type, user within a group, group,application type, content type, or any other criteria or measure and/orany combination thereof. In some embodiments, the service controlleralso facilitates coordination of various device QoS requests with othernetwork elements/functions for QoS implementation and management toprovide for an end to end QoS solution.

In some embodiments, QoS can be symmetric for two mobile devices orasymmetric. In some embodiments, QoS resource availability can be fromcommunications devices, BTS(s), other network functions (e.g., servicecontrol, service controller and/or any other network elements/functions)or any combination thereof. In some embodiments, the service controllerprovides QoS demand information to another network element/function. Insome embodiments, the service controller provides the central aggregatorand policy decision point (PDP). In some embodiments, the servicecontroller controls (e.g., at least in part) QoS related functions forcommunications devices, BTS(s), and/or a combination of both.

In some embodiments, charging (e.g., monitoring and/or determiningassociating charging or billing) for QoS service usage/transactions isdetermined using various techniques described herein. For example, theservice processor can assist in charging for QoS activities. In someembodiments, the service processor uses device assisted Charging DataRecords (CDRs) or micro-CDRs to assist in charging for QoS activities(e.g., using QoS class related transaction codes), as described hereinwith respect to various embodiments. In some embodiments, charging forQoS is performed in whole or in part by one or more networkelements/functions (e.g., service controller, SGSN/GGSN/other gateways,and/or billing interfaces/servers).

In some embodiments, service usage information includes network basedservice usage information. In some embodiments, the network basedservice usage information includes network based CDRs. In someembodiments, service usage information includes device based serviceusage information. In some embodiments, device based service usageinformation includes device assisted CDRs, also referred to herein asmicro-CDRs, as described herein. In some embodiments, micro-CDRs areused for CDR mediation or reconciliation that provides for service usageaccounting on any device activity that is desired (e.g., providinggranular service usage information, such as based on application layerservice usage monitoring, transaction service usage monitoring, QoSactivities/sessions/transactions, and/or other types of service usageinformation). In some embodiments, each device includes a serviceprocessor (e.g., a service processor executed on a processor of acommunications device, such as a mobile device or an intermediatenetworking device that can communicate with a wireless network).

In some embodiments, each device activity that is desired to beassociated with a billing event (e.g., for a QoS related billing event)is assigned a micro-CDR transaction code, and the service processor isprogrammed to account for that activity associated with that transactioncode (e.g., various transaction codes can be associated with serviceusage associated with certain services, applications, and/or based onQoS classes or priorities, respectively, which can be used for providinggranular service usage for these various Internet/network basedservices/sites/transactions and/or any other Internet/network basedservices/sites, which can include transactional based services). Forexample, using these techniques, as described herein, essentially anytype of device activity (e.g., including QoS classes and prioritization)can be individually accounted for and/or controlled (e.g., throttled,restricted, and/or otherwise controlled as desired). In someembodiments, the service processor periodically reports (e.g., duringeach heartbeat or based on any other periodic, push, and/or pullcommunication technique(s)) micro-CDR usage measures to, for example, aservice controller or some other network element/function. In someembodiments, the service controller reformats the heartbeat micro-CDRusage information into a valid CDR format (e.g., a CDR format that isused and can be processed by an SGSN or GGSN or some other authorizednetwork element/function for CDRs) and then transmits the reformattedmicro-CDRs to a network element/function for performing CDR mediation.

In some embodiments, CDR mediation is used to properly account for themicro-CDR service usage information by depositing it into an appropriateservice usage account and deducting it from the user device bulk serviceusage account. For example, this technique provides for a flexibleservice usage billing solution that uses pre-existing solutions for CDRmediation and billing. For example, the billing system can process themediated CDR feed from CDR mediation, apply the appropriate accountbilling codes to the aggregated micro-CDR information that was generatedby the device, and then generate billing events in a manner that doesnot require changes to existing billing systems, infrastructures, andtechniques (e.g., using new transaction codes to label the new deviceassisted billing capabilities).

In some embodiments, the various QoS techniques performed on or by thecommunications device (e.g., using a service processor to provide orassist in providing QoS session provisioning, QoS policy management, QoSpolicy enforcement, and/or QoS charging, such as QoS charging recordsand reports) are verified.

For example, a QoS request, QoS related policy rules (e.g., QoS activitymap, QoS related service plan and/or service policy settings) andimplementation, QoS policy enforcement, and QoS charging are verified(e.g., periodically, per transaction, and/or based on some othercriteria/metric). In some embodiments, verification techniques includeone or more of the following: compare a network based service usagemeasure with a first service policy associated with the communicationsdevice, compare a device assisted service usage measure with the firstservice policy, compare the network based service usage measure to thedevice assisted service usage measure, perform a test and confirm adevice assisted service usage measure based on the test, perform a UserInterface (UI) notification (e.g., which can include a userauthentication, password, question/answer challenge, and/or otherauthentication technique) and other similar verification techniques aswill now be apparent. Accordingly, in some embodiments, QoS for DAS“closes the loop” for verification of various QoS related techniques,such as QoS requests, QoS grants, QoS usage, and/or QoS charging. Insome embodiments, the service processor and the service controller serveas a verifiable QoS management/coordination system for other QoSelements/functions in network. In some embodiments, if such or otherverification techniques determine or assist in determining that a QoSrequest, QoS report, and/or QoS policy behavior does not match expectedrequests, reports, and/or policy, then responsive actions can beperformed, for example, the communications device can be suspended,quarantined and/or flagged for further analysis/scrutiny to determinewhether the device is malfunctioning, needs updating, has been tamperedwith or compromised, is infected with malware, and/or if any otherproblem exists.

In some embodiments, the communications device (e.g., the serviceprocessor) maintains a QoS flow table that associates or maps deviceactivity to QoS level/class to RAB/QoS channel, and, in someembodiments, the communications device also informs a QoS managementnetwork function/element of the relative priority of the QoS flows forthe communications device (e.g., based on or using the QoS flow table).In some embodiments, the service controller receives or collectsinformation from the communications device and maintains such a QoS flowtable for the communications device and in some embodiments, the servicecontroller also informs a QoS management network function/element of therelative priority of the QoS flows for the communications device (e.g.,based on or using the QoS flow table). In some embodiments, flows can beassigned to activities originating at the communications device in atransparent way, or simply by activity class or user preference, orusing other techniques.

In some embodiments, the communications device maintains a table of QoSbilling rates, scheduled transmission times, and/other QoS relatedinformation to implement an overlay MAC at the data networking level tomanage QoS on legacy networks that are not QoS MAC enabled and/or do nothave the various functionality to support QoS controls (e.g., and suchtechniques can also be used to provide for QoS functionality acrossdifferent networks). In some embodiments, QoS related policies areexchanged between roaming and home service controllers to facilitate QoSsupport while roaming on a non-home network(s).

In some embodiments, the communications device serves as a networkcapacity indicator (e.g., collecting network capacity information for alocal cell and communicating or reporting that network capacityinformation to the service controller). For example, permanent localcell communications devices can be placed in local cell areas to augmentlegacy equipment for such network capacity indicator/reportingfunctions.

In some embodiments, service partners and/or service providers cansubsidize in whole or in part to upgrade a given user or group of usersto better QoS related service level agreement(SLA)/class for a preferreddestination. In some embodiments, based on monitored service usageand/or other monitored behavior of the communications device, suchsubsidized QoS upgrade/offers can be presented to a user of thecommunications device (e.g., as an incentive/reward for desired orpreferred user behavior or for other reasons).

In some embodiments, QoS charging is based on QoS channel/reservation,service flow, or RAB charging (e.g., single flow per RAB, multi-flow perRAB, multi-RAB per flow). In some embodiments, charging is based on oneor more of the following: user service class request, traffic volume andclass, time and class, network capacity (e.g., network busy state) andclass, time of day and class, location, traffic type, application type,application class, destination, destination type, partner service,and/or other criteria/measures. In some embodiments, QoS charging isverified using the various verification techniques described herein(e.g., test charging events). In some embodiments, QoS charging is bydata usage (e.g., by Megabyte (MB)), service flow by time by QoS class,speed by time, and/or other criteria/measures.

In some embodiments, QoS for DAS includes coordinating functions withone or more of the following: DAS elements/functions, Radio AccessNetwork (RAN), Transport network, Core network, GRX network, IPXnetwork, and/or other networks/elements/functions.

FIG. 2 illustrates another functional diagram of another networkarchitecture for providing quality of service (QoS) for device assistedservices (DAS) in accordance with some embodiments. In some embodiments,QoS for DAS techniques described herein are implemented using thenetwork architecture shown in FIG. 2.

As shown, FIG. 2 includes various devices 100 including serviceprocessors 115. For example, devices 100 can include various types ofmobile devices, such as phones, PDAs, computing devices, laptops, netbooks, tablets, cameras, music/media players, GPS devices, networkedappliances, and any other networked device; and/or devices 100 caninclude various types of intermediate networking devices, as describedherein. The devices 100 are in communication with service control 210and central provider access and core networks 220. Service policies andaccounting functions 230 are also provided in communication with thecentral provider access and core networks 220. For example, devices 100can communicate via the central provider access and core networks 220 tothe Internet 120 for access to various Internet sites/services 240(e.g., Google sites/services, Yahoo sites/services, Blackberry services,Apple iTunes and AppStore, Amazon.com, FaceBook, and/or any otherInternet service or other network facilitated service).

In some embodiments, FIG. 2 provides a wireless network architecturethat supports partitioned device groups, in which each device group canbe provided independent and secure management of transparentreconciliation. Those of ordinary skill in the art will appreciate thatvarious other network architectures can be used for providing devicegroup partitions and a settlement platform, and FIG. 2 is illustrativeof just another such example network architecture for which device grouppartitions and settlement platform techniques described herein can beprovided.

In some embodiments, a service provider selects who receives areconciliation report of activations and usage by service plan type. Insome embodiments, service usage information (e.g., based on CDRs and/ormicro-CDRs or other service usage measures) are used for service planbilling and for reconciliation reports. In some embodiments, differentservice plans on the same device (e.g., device 100) can be sent todifferent partners or the same partner. In some embodiments,multi-device and multi-user reconciliation capabilities are provided. Insome embodiments, a settlement platform service is provided. In someembodiments, various revenue share techniques as described herein areprovided (e.g., implemented using a settlement platform service, using,for example, service policies and accounting functions 230).

In some embodiments, partitioned device groups are provided. In someembodiments, each partitioned group of devices (e.g., mobile devices100) can be uniquely managed with secure admin log-ins. In someembodiments, multi-device, multi-user accounting is provided. In someembodiments, capabilities are provided to supportmulti-party/multi-service reconciliation records to carriers and carrierpartners, which can also support various service/transactional revenueshare techniques (e.g., for reducing or eliminating the up-front subsidyand associated up-front subsidy risk of certain bounty models). In someembodiments, service usage and profitability analytics are provided(e.g., using aggregated CDRs/micro-CDRs and service policies andaccounting functions 230). For example, a partitioned beta test group ofdevices can be tested and optimized for various service usage policiesand/or service plans, and then the optimized service usage policiesand/or service plans can be published to an entire or larger devicegroup. In some embodiments, a carrier can be provided a carrier brandeddevice group, and/or a MVNO can be provided a MVNO branded device group.

FIG. 3 illustrates another functional diagram of a QoS for DASarchitecture 300 including a device based service processor 115 and aservice controller 122 for providing quality of service (QoS) for deviceassisted services (DAS) in accordance with some embodiments. In someembodiments, QoS for DAS techniques described herein are implementedusing the functions/elements shown in FIG. 3.

For example, the architecture 300 provides a relatively full featureddevice based service processor implementation and service controllerimplementation. As shown, this corresponds to a networking configurationin which the service controller 122 is connected to the Internet 120 andnot directly to the access network 1610. As shown, a data plane (e.g.,service traffic plane) communication path is shown in solid lineconnections and control plane (e.g., service control plane)communication path is shown in dashed line connections. As will beapparent, the division in functionality between one device agent andanother is based on, for example, design choices, networkingenvironments, devices and/or services/applications, and variousdifferent combinations can be used in various different implementations.For example, the functional lines can be re-drawn in any way that theproduct designers see fit. As shown, this includes certain divisions andfunctional breakouts for device agents as an illustrativeimplementation, although other, potentially more complex, embodimentscan include different divisions and functional breakouts for deviceagent functionality specifications, for example, in order to managedevelopment specification and testing complexity and workflow. Inaddition, the placement of the agents that operate, interact with ormonitor the data path can be moved or re-ordered in various embodiments.For example, the functional elements shown in FIG. 3 are described belowwith respect to FIGS. 10 and 11.

As shown in FIG. 3, service processor 115 includes a service controldevice link 1691. For example, as device based service controltechniques involving supervision across a network become moresophisticated, it becomes increasingly important to have an efficientand flexible control plane communication link between the device agentsand the network elements communicating with, controlling, monitoring, orverifying service policy. In some embodiments, the service controldevice link 1691 provides the device side of a system for transmissionand reception of service agent to/from network element functions. Insome embodiments, the traffic efficiency of this link is enhanced bybuffering and framing multiple agent messages in the transmissions. Insome embodiments, the traffic efficiency is further improved bycontrolling the transmission frequency or linking the transmissionfrequency to the rate of service usage or traffic usage. In someembodiments, one or more levels of security or encryption are used tomake the link robust to discovery, eavesdropping or compromise. In someembodiments, the service control device link 1691 also provides thecommunications link and heartbeat timing for the agent heartbeatfunction. As discussed below, various embodiments disclosed herein forthe service control device link 1691 provide an efficient and securesolution for transmitting and receiving service policy implementation,control, monitoring and verification information with other networkelements.

As shown in FIG. 3, the service controller 122 includes a servicecontrol server link 1638. In some embodiments, device based servicecontrol techniques involving supervision across a network (e.g., on thecontrol plane) are more sophisticated, and for such it is increasinglyimportant to have an efficient and flexible control plane communicationlink between the device agents (e.g., of the service processor 115) andthe network elements (e.g., of the service controller 122) communicatingwith, controlling, monitoring, or verifying service policy. For example,the communication link between the service control server link 1638 ofservice controller 122 and the service control device link 1691 of theservice processor 115 can provide an efficient and flexible controlplane communication link, a service control link 1653 as shown in FIG.3, and, in some embodiments, this control plane communication linkprovides for a secure (e.g., encrypted) communications link forproviding secure, bidirectional communications between the serviceprocessor 115 and the service controller 122. In some embodiments, theservice control server link 1638 provides the network side of a systemfor transmission and reception of service agent to/from network elementfunctions. In some embodiments, the traffic efficiency of this link isenhanced by buffering and framing multiple agent messages in thetransmissions (e.g., thereby reducing network chatter). In someembodiments, the traffic efficiency is further improved by controllingthe transmission frequency and/or linking the transmission frequency tothe rate of service usage or traffic usage. In some embodiments, one ormore levels of security and/or encryption are used to secure the linkagainst potential discovery, eavesdropping or compromise ofcommunications on the link. In some embodiments, the service controlserver link 1638 also provides the communications link and heartbeattiming for the agent heartbeat function.

In some embodiments, the service control server link 1638 provides forsecuring, signing, encrypting and/or otherwise protecting thecommunications before sending such communications over the servicecontrol link 1653. For example, the service control server link 1638 cansend to the transport layer or directly to the link layer fortransmission. In another example, the service control server link 1638further secures the communications with transport layer encryption, suchas TCP TLS or another secure transport layer protocol. As anotherexample, the service control server link 1638 can encrypt at the linklayer, such as using IPSEC, various possible VPN services, other formsof IP layer encryption and/or another link layer encryption technique.

As shown in FIG. 3, the service controller 122 includes an accesscontrol integrity server 1654 (e.g., service policy security server). Insome embodiments, the access control integrity server 1654 collectsdevice information on service policy, service usage, agentconfiguration, and/or agent behavior. For example, the access controlintegrity server 1654 can cross check this information to identifyintegrity breaches in the service policy implementation and controlsystem. In another example, the access control integrity server 1654 caninitiate action when a service policy violation or a system integritybreach is suspected.

In some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) acts on access controlintegrity agent 1694 (e.g., service policy security agent) reports anderror conditions. Many of the access control integrity agent 1654 checkscan be accomplished by the server. For example, the access controlintegrity agent 1654 checks include one or more of the following:service usage measure against usage range consistent with policies(e.g., usage measure from the network and/or from the device);configuration of agents; operation of the agents; and/or dynamic agentdownload.

In some embodiments, the access control integrity server 1654 (e.g.,and/or some other agent of service controller 122) verifies deviceservice policy implementations by comparing various service usagemeasures (e.g., based on network monitored information, such as by usingIPDRs or CDRs, and/or local service usage monitoring information)against expected service usage behavior given the policies that areintended to be in place. For example, device service policyimplementations can include measuring total QoS data passed, QoS datapassed in a period of time, IP addresses, data per IP address, and/orother measures such as location, downloads, email accessed, URLs, andcomparing such measures expected service usage behavior given thepolicies that are intended to be in place.

In some embodiments, the access control integrity server 1654 (and/orsome other agent of service controller 122) verifies device servicepolicy, and the verification error conditions that can indicate amismatch in QoS service measure and QoS service policy include one ormore of the following: unauthorized network access (e.g., access beyondambient service policy limits); unauthorized network speed (e.g.,average speed beyond service policy limit); network data amount does notmatch QoS policy limit (e.g., device not stop at limit withoutre-up/revising service policy); unauthorized network address;unauthorized service usage (e.g., VOIP, email, and/or web browsing);unauthorized application usage (e.g., email, VOIP, email, and/or web);service usage rate too high for plan, and policy controller notcontrolling/throttling it down; and/or any other mismatch in servicemeasure and service policy. Accordingly, in some embodiments, the accesscontrol integrity server 1654 (and/or some other agent of servicecontroller 122) provides a policy/service control integrity service tocontinually (e.g., periodically and/or based on trigger events) verifythat the service control of the device has not been compromised and/oris not behaving out of policy.

As shown in FIG. 3, service controller 122 includes a service historyserver 1650 (e.g., charging server). In some embodiments, the servicehistory server 1650 collects and records service usage or serviceactivity reports from the Access Network AAA Server 1621 and the ServiceMonitor Agent 1696. For example, although service usage history from thenetwork elements can in certain embodiments be less detailed thanservice history from the device, the service history from the networkcan provide a valuable source for verification of device service policyimplementation, because, for example, it is extremely difficult for adevice error or compromise event on the device to compromise the networkbased equipment and software. For example, service history reports fromthe device can include various service tracking information, assimilarly described above. In some embodiments, the service historyserver 1650 provides the service history on request to other serversand/or one or more agents. In some embodiments, the service historyserver 1650 provides the service usage history to the device servicehistory 1618 (e.g., CDR feed and CDR mediation). In some embodiments,for purposes of facilitating the activation tracking service functions(described below), the service history server 1650 maintains a historyof which networks the device has connected to. For example, this networkactivity summary can include a summary of the networks accessed,activity versus time per connection, and/or traffic versus time perconnection. As another example, this activity summary can further beanalyzed or reported to estimate the type of service plan associatedwith the traffic activity for the purpose of bill sharingreconciliation.

As shown in FIG. 3, service controller 122 includes a QoS policymanagement server 1652 (e.g., policy decision point (PDP) server). Insome embodiments, the QoS policy management server 1652 transmitspolicies to the service processor 115 via the service control link 1653.In some embodiments, the policy management server 1652 manages policysettings on the device (e.g., various policy settings as describedherein with respect to various embodiments) in accordance with a deviceservice profile. In some embodiments, the policy management server 1652sets instantaneous policies on policy implementation agents (e.g.,policy implementation agent 1690). For example, the policy managementserver 1652 can issue policy settings, monitor service usage and, ifnecessary, modify policy settings. For example, in the case of a userwho prefers for the network to manage their service usage costs, or inthe case of any adaptive policy management needs, the policy managementserver 1652 can maintain a relatively high frequency of communicationwith the device to collect traffic and/or service measures and issue newpolicy settings. In this example, device monitored service measures andany user service policy preference changes are reported, periodicallyand/or based on various triggers/events/requests, to the policymanagement server 1652. In this example, user privacy settings generallyrequire secure communication with the network (e.g., a secure servicecontrol link 1653), such as with the policy management server 1652, toensure that various aspects of user privacy are properly maintainedduring such configuration requests/policy settings transmitted over thenetwork. For example, information can be compartmentalized to servicepolicy management and not communicated to other databases used for CRMfor maintaining user privacy.

In some embodiments, the policy management server 1652 provides adaptivepolicy management on the device. For example, the policy managementserver 1652 can issue policy settings and objectives and rely on thedevice based policy management (e.g., service processor 115) for some orall of the policy adaptation. This approach can require less interactionwith the device thereby reducing network chatter on the service controllink 1653 for purposes of device policy management (e.g., networkchatter is reduced relative to various server/network based policymanagement approaches described above). This approach can also providerobust user privacy embodiments by allowing the user to configure thedevice policy for user privacy preferences/settings so that, forexample, sensitive information (e.g., geo-location data, websitehistory) is not communicated to the network without the user's approval.In some embodiments, the policy management server 1652 adjusts servicepolicy based on time of day. In some embodiments, the policy managementserver 1652 receives, requests or otherwise obtains a measure of networkavailability and adjusts traffic shaping policy and/or other policysettings based on available network capacity.

As shown in FIG. 3, service controller 122 includes a network trafficanalysis server 1656. In some embodiments, the network traffic analysisserver 1656 collects/receives service usage history for devices and/orgroups of devices and analyzes the service usage. In some embodiments,the network traffic analysis server 1656 presents service usagestatistics in various formats to identify improvements in networkservice quality and/or service profitability. In some embodiments, thenetwork traffic analysis server 1656 estimates the service qualityand/or service usage for the network under variable settings onpotential service policies. In some embodiments, the network trafficanalysis server 1656 identifies actual or potential service behaviors byone or more devices that are causing problems for overall networkservice quality or service cost.

As shown in FIG. 3, Service Analysis, Test & Download 122B includes abeta test server 1658 (e.g., policy creation point and beta testserver). In some embodiments, the beta test server 1658 publishescandidate service plan policy settings to one or more devices. In someembodiments, the beta test server 1658 provides summary reports ofnetwork service usage or user feedback information for one or morecandidate service plan policy settings. In some embodiments, the betatest server 1658 provides a mechanism to compare the beta test resultsfor different candidate service plan policy settings or select theoptimum candidates for further policy settings optimization.

As shown in FIG. 3, service controller 122 includes a service downloadcontrol server 1660 (e.g., a service software download control server).In some embodiments, the service download control server 1660 provides adownload function to install and/or update service software elements(e.g., the service processor 115 and/or agents/components of the serviceprocessor 115) on the device, as described herein.

As shown in FIG. 3 service controller 122 includes a billing eventserver 1662 (e.g., micro-CDR server). In some embodiments, the billingevent server 1662 collects billing events, provides service planinformation to the service processor 115, provides service usage updatesto the service processor 115, serves as interface between device andcentral billing server 1619, and/or provides trusted third partyfunction for certain ecommerce billing transactions.

As shown in FIG. 3, the Access Network HLR AAA server 1621 is in networkcommunication with the access network 1610. In some embodiments, theAccess Network AAA server 1621 provides the necessary access network AAAservices (e.g., access control and authorization functions for thedevice access layer) to allow the devices onto the central provideraccess network and the service provider network. In some embodiments,another layer of access control is required for the device to gainaccess to other networks, such as the Internet, a corporate networkand/or a machine to machine network. This additional layer of accesscontrol can be implemented, for example, by the service processor 115 onthe device. In some embodiments, the Access Network AAA server 1621 alsoprovides the ability to suspend service for a device and resume servicefor a device based on communications received from the servicecontroller 122. In some embodiments, the Access Network AAA server 1621also provides the ability to direct routing for device traffic to aquarantine network or to restrict or limit network access when a devicequarantine condition is invoked. In some embodiments, the Access NetworkAAA server 1621 also records and reports device network service usage(e.g., device network service usage can be reported to the deviceservice history 1618).

As shown in FIG. 3, the device service history 1618 is in networkcommunication with the access network 1610. In some embodiments, thedevice service history 1618 provides service usage data records used forvarious purposes in various embodiments. In some embodiments, the deviceservice history 1618 is used to assist in verifying service policyimplementation. In some embodiments, the device service history 1618 isused to verify service monitoring. In some embodiments, the deviceservice history 1618 is used to verify billing records and/or billingpolicy implementation. In some embodiments, the device service history1618 is used to synchronize and/or verify the local service usagecounter.

As shown in FIG. 3, the central billing 1619 (e.g., central providerbilling server) is in network communication with the access network1610. In some embodiments, the central provider billing server 1619provides a mediation function for central provider billing events. Forexample, the central provider billing server 1619 can accept serviceplan changes. In some embodiments, the central provider billing server1619 provides updates on device service usage, service plan limitsand/or service policies. In some embodiments, the central providerbilling server 1619 collects billing events, formulates bills, billsservice users, provides certain billing event data and service planinformation to the service controller 122 and/or device 100.

As shown in FIG. 3, in some embodiments, modem selection and control1811 (e.g., in communication with connection manager 1804 as shown)selects the access network connection and is in communication with themodem firewall 1655, and modem drivers 1831, 1815, 1814, 1813, 1812convert data traffic into modem bus traffic for one or more modems andare in communication with the modem selection and control 1811. In someembodiments, different profiles are selected based on the selectednetwork connection (e.g., different service profiles/policies for WWAN,WLAN, WPAN, Ethernet and/or DSL network connections), which is alsoreferred to herein as multimode profile setting. For example, serviceprofile settings can be based on the actual access network (e.g., homeDSL/cable or work network) behind the Wi-Fi not the fact that it isWi-Fi (e.g., or any other network, such as DSL/cable, satellite, orT-1), which is viewed as different than accessing a Wi-Fi network at thecoffee shop. For example, in a Wi-Fi hotspot situation in which thereare a significant number of users on a DSL or T-1 backhaul, the servicecontroller can sit in a service provider cloud or an MVNO cloud, theservice controls can be provided by a VSP capability offered by theservice provider or the service controller can be owned by the hotspotservice provider that uses the service controller on their own withoutany association with an access network service provider. For example,the service processors can be controlled by the service controller todivide up the available bandwidth at the hotspot according to QoS oruser sharing rules (e.g., with some users having higher differentiatedpriority (e.g., potentially for higher service payments) than otherusers). As another example, ambient services (e.g., as similarlydescribed herein) can be provided for the hotspot for verified serviceprocessors.

In some embodiments, the service processor 115 and service controller122 are capable of assigning multiple service profiles associated withmultiple service plans that the user chooses individually or incombination as a package. For example, a device 100 starts with ambientservices that include free transaction services wherein the user paysfor transactions or events rather than the basic service (e.g., a newsservice, eReader, PND service, pay as you go session Internet) in whicheach service is supported with a bill by account capability to correctlyaccount for any subsidized partner billing to provide the transactionservices (e.g., Barnes and Noble may pay for the eReader service andoffer a revenue share to the service provider for any book or magazinetransactions purchased from the device 100). In some embodiments, thebill by account service can also track the transactions and, in someembodiments, advertisements for the purpose of revenue sharing, allusing the service monitoring capabilities disclosed herein. Afterinitiating services with the free ambient service discussed above, theuser may later choose a post-pay monthly Internet, email and SMSservice. In this case, the service controller 122 would obtain from thebilling system 123 in the case of network based billing (e.g., or theservice controller 122 billing event server 1622 in the case of devicebased billing) the billing plan code for the new Internet, email and SMSservice. In some embodiments, this code is cross referenced in adatabase (e.g., the policy management server 1652) to find theappropriate service profile for the new service in combination with theinitial ambient service. The new superset service profile is thenapplied so that the user maintains free access to the ambient services,and the billing partners continue to subsidize those services, the useralso gets access to Internet services and may choose the service controlprofile (e.g., from one of the embodiments disclosed herein). Thesuperset profile is the profile that provides the combined capabilitiesof two or more service profiles when the profiles are applied to thesame device 100 service processor. In some embodiments, the device 100(service processor 115) can determine the superset profile rather thanthe service controller 122 when more than one “stackable” service isselected by the user or otherwise applied to the device. The flexibilityof the service processor 115 and service controller 122 embodimentsdescribed herein allow for a large variety of service profiles to bedefined and applied individually or as a superset to achieve the desireddevice 100 service features.

As shown in FIG. 3, an agent communication bus 1630 represents afunctional description for providing communication for the variousservice processor 115 agents and functions. In some embodiments, asrepresented in the functional diagram illustrated in FIG. 3, thearchitecture of the bus is generally multipoint to multipoint so thatany agent can communicate with any other agent, the service controlleror in some cases other components of the device, such user interface1697 and/or modem components. As described below, the architecture canalso be point to point for certain agents or communication transactions,or point to multipoint within the agent framework so that all agentcommunication can be concentrated, or secured, or controlled, orrestricted, or logged or reported. In some embodiments, the agentcommunication bus is secured, signed, encrypted, hidden, partitioned,and/or otherwise protected from unauthorized monitoring or usage. Insome embodiments, an application interface agent (not shown) is used toliterally tag or virtually tag application layer traffic so that thepolicy implementation agent(s) 1690 has the necessary information toimplement selected traffic shaping solutions. In some embodiments, anapplication interface agent (not shown) is in communication with variousapplications, including a TCP application 1604, an IP application 1605,and a voice application 1602.

As shown in FIG. 3, service processor 115 includes a QoS API and OSstack interface 1693. In some embodiments, QoS API and OS stackinterface 1693 provides the QoS API functionality as similarly describedherein with respect to various embodiments. In some embodiments, the QoSAPI is used to report back QoS availability to applications. As shown,service processor 115 also includes a QoS router 1698 (e.g., QoS routeragent/function) and a policy decision point (PDP) agent 1692. In someembodiments, QoS router 1698 provides the QoS router functionality assimilarly described herein with respect to various embodiments. In someembodiments, the QoS router supports multiple QoS channels (e.g., one ormore provisioned/allocated QoS links forming a QoS channel between thedevice and the desired end point, such as an accesspoint/BTS/gateway/network for a single ended QoS channel or othercommunication device for an end to end QoS channel, depending on the QoSconnection/network support/availability/etc.). In some embodiments, theQoS router supports multiple QoS channels, which can each have differentQoS classes/levels. In some embodiments, the QoS router routesapplication/service usage traffic to an appropriate QoS channel. In someembodiments, the QoS router determines the routing/mapping based on, forexample, one or more of the following: a QoS API request, a QoS activitymap, a user request, a service plan, a service profile, service policysettings, network capacity, service controller or other intermediate QoSnetwork element/function/device, and/or any other criteria/measure, assimilarly described herein with respect to various embodiments. In someembodiments, multiple different applications/services are routed to aparticular QoS channel using various techniques described herein. Insome embodiments, different applications/services are routed todifferent QoS channels using various techniques described herein. Insome embodiments, the QoS router assists in managing and/or optimizingQoS usage for the communications device. In some embodiments, the QoSrouter assists in managing and/or optimizing QoS usage across multiplecommunications devices (e.g., based on network capacity for a given cellarea/base station or other access point). In some embodiments, PDP agent1692 provides the PDP agent functionality as similarly described hereinwith respect to various embodiments. As shown, QoS for DAS architecture330 also includes a suspend resume interface 320, network QoSprovisioning interfaces 330; an activation/suspend resume server 340 andbilling interface server 350 in the service controller 122A; and asuspend/resume interface 320 and network QoS provisioning interfaces 330for providing the various QoS techniques described herein.

In some embodiments, device assisted services (DAS) techniques forproviding an activity map for classifying or categorizing service usageactivities to associate various monitored activities (e.g., by URL, bynetwork domain, by website, by network traffic type, by application orapplication type, and/or any other service usage activitycategorization/classification) with associated IP addresses areprovided. In some embodiments, a policy control agent (not shown),service monitor agent 1696 (e.g., charging agent), or another agent orfunction (or combinations thereof) of the service processor 115 providesa DAS activity map. In some embodiments, a policy control agent (notshown), service monitor agent, or another agent or function (orcombinations thereof) of the service processor provides an activity mapfor classifying or categorizing service usage activities to associatevarious monitored activities (e.g., by Uniform Resource Locator (URL),by network domain, by website, by network traffic type, by applicationor application type, and/or any other service usage activityclassification/categorization) with associated IP addresses. In someembodiments, a policy control agent, service monitor agent, or anotheragent or function (or combinations thereof) of the service processordetermines the associated IP addresses for monitored service usageactivities using various techniques to snoop the DNS request(s) (e.g.,by performing such snooping techniques on the device 100 the associatedIP addresses can be determined without the need for a network requestfor a reverse DNS lookup). In some embodiments, a policy control agent,service monitor agent, or another agent or function (or combinationsthereof) of the service processor records and reports IP addresses orincludes a DNS lookup function to report IP addresses or IP addressesand associated URLs for monitored service usage activities. For example,a policy control agent, service monitor agent, or another agent orfunction (or combinations thereof) of the service processor candetermine the associated IP addresses for monitored service usageactivities using various techniques to perform a DNS lookup function(e.g., using a local DNS cache on the monitored device 100). In someembodiments, one or more of these techniques are used to dynamicallybuild and maintain a DAS activity map that maps, for example, URLs to IPaddresses, applications to IP addresses, content types to IP addresses,and/or any other categorization/classification to IP addresses asapplicable. In some embodiments, the DAS activity map is used forvarious DAS traffic control and/or throttling techniques as describedherein with respect to various embodiments. In some embodiments, the DASactivity map is used to provide the user various UI related informationand notification techniques related to service usage as described hereinwith respect to various embodiments. In some embodiments, the DASactivity map is used to provide service usage monitoring,prediction/estimation of future service usage, service usage billing(e.g., bill by account and/or any other service usage/billingcategorization techniques), DAS techniques for ambient services usagemonitoring, DAS techniques for generating micro-CDRs, and/or any of thevarious other DAS related techniques as described herein with respect tovarious embodiments.

In some embodiments, all or a portion of the service processor 115functions disclosed herein are implemented in software. In someembodiments, all or a portion of the service processor 115 functions areimplemented in hardware. In some embodiments, all or substantially allof the service processor 115 functionality (e.g., as discussed herein)is implemented and stored in software that can be performed on (e.g.,executed by) various components in device 100. In some embodiments, itis advantageous to store or implement certain portions or all of serviceprocessor 115 in protected or secure memory so that other undesiredprograms (e.g., and/or unauthorized users) have difficulty accessing thefunctions or software in service processor 115. In some embodiments,service processor 115, at least in part, is implemented in and/or storedon secure non-volatile memory (e.g., non volatile memory can be securenon-volatile memory) that is not accessible without pass keys and/orother security mechanisms. In some embodiments, the ability to load atleast a portion of service processor 115 software into protectednon-volatile memory also requires a secure key and/or signature and/orrequires that the service processor 115 software components being loadedinto non-volatile memory are also securely encrypted and appropriatelysigned by an authority that is trusted by a secure software downloaderfunction, such as service downloader 1663 as shown in FIG. 3. In someembodiments, a secure software download embodiment also uses a securenon-volatile memory. Those of ordinary skill in the art will alsoappreciate that all memory can be on-chip, off-chip, on-board and/oroff-board.

FIGS. 4A through 4C illustrates a functional diagram for providingquality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments. In some embodiments, QoS for DAStechniques described herein are implemented using the networkarchitecture shown in FIGS. 4A through 4C.

Referring to FIG. 4A, in some embodiments, QoS functionality isperformed at the communications device 100 using service processor 115as similarly described herein. For example, the service processor 115determines whether or not a QoS request is authorized (e.g., based onthe associated service plan and/or other criteria/measures). If the QoSrequest is authorized, then the service processor 115 communicates withthe base station (BTS) 125 to send the QoS request (e.g., a RAB ormulti-RAB reservation request) to the local BTS. The BTS determineswhether to accept or deny the QoS request (e.g., based on networkcapacity, such as using a first come first service QoS/network bandwidthor best effort access policy or other techniques, and/or othercriteria/measures). The BTS responds to the QoS request accordingly. Ifthe QoS request is granted, the QoS session can be initiated assimilarly described herein. In some embodiments, the service processor115 also performs various QoS charging functions using varioustechniques described herein, and the service processor 115 periodicallysends QoS charging records or reports to the service controller 122. Insome embodiments, the service processor 115 and the QoS relatedfunctions performed by the service processor 115 are periodicallyverified using the various techniques described herein.

Referring to FIG. 4B, FIG. 4B is similar to FIG. 4A except that theservice controller 122 is also shown to be in communication with theservice processor 115 of the communications device 100, which canprovide for the download and periodically updating of the QoS rulesand/or other service plan/profile/policy information that can includeQoS related information. In some embodiments, the service processor 115also performs various QoS charging functions using various techniquesdescribed herein, and the service processor 115 periodically sends QoScharging records or reports to the service controller 122. In someembodiments, the service processor 115 and the QoS related functionsperformed by the service processor 115 are periodically verified usingthe various techniques described herein.

Referring to FIG. 4C, at 410, the service processor 115 sends a QoSrequest to the service controller 122 (e.g., the service processor canalso (at least in part) determine whether the QoS request is authorizedas similarly described with respect to FIG. 4A). At 420, the servicecontroller 122 sends the QoS request to the BTS 125 if it is determinedthat the QoS request is authorized using various techniques describedherein and/or whether the BTS 125 has network capacity for the QoSrequest. For example, the service controller can provide a centralpolicy decision point function for QoS related activities (e.g., basedon QoS prioritization, network capacity, and/or othercriteria/measures/policies). At 430, the service controller 122communicates the response to the QoS request accordingly. At 440, if theQoS request was approved, the device 100 initiates the QoS session(e.g., using a RAB or multi-RAB reservation) via the BTS 125. In someembodiments, the service processor 115 also performs various QoScharging functions using various techniques described herein, and theservice processor 115 periodically sends QoS charging records or reportsto the service controller 122. In some embodiments, the serviceprocessor 115 and the QoS related functions performed by the serviceprocessor 115 are periodically verified using the various techniquesdescribed herein.

In some embodiments, QoS techniques as described herein are implementedin the device (e.g., using the service processor 115) and one or moreother network elements/functions, such as the BTS 125, servicecontroller 125, RAN, SGSN/GGSN/other gateways and/or other networkelements/functions, in which various of the QoS related functions can bedistributed or allocated to such network elements/functions based onvarious design/network architecture approaches as will now be apparentto one of ordinary skill in the art, in which QoS related activitiesand/or functions at the device 100 are verified using variousverification techniques described herein.

In some embodiments, the device determines QoS availability by directlyQuerying QoS link reservation equipment in the network (e.g., an accesspoint, such as the BTS 125). In some embodiments, the device determinesQoS availability based on an intermediate network function thatcoordinates QoS requests with one or more network QoS link resources. Insome embodiments, the device requests a QoS reservation in advance ofQoS link establishment with one or more QoS network link resources. Insome embodiments, in response to a QoS request, a QoS channel isreported as available only if/after it is determined that the necessaryone or more QoS links required to create the QoS channel are available,and, for example, the QoS channel can then be reserved based on aconfirmation or automatically be reserved in response to the QoSrequest.

FIG. 5 illustrates a functional diagram for generating a QoS activitymap for quality of service (QoS) for device assisted services (DAS) inaccordance with some embodiments. In particular, FIG. 5 illustratestechniques for mapping a service plan or a set of service planpolicies/rules for QoS 510 to a set of QoS activity rules 530. As shown,a set of QoS rules/QoS related device state information 510 (e.g., a setof associated service plan, service plan usage, other state such asnetwork capacity or forecasted demand or time of day/day of week,activity usage, QoS level, and/or user preferences) is mapped using aQoS mapping function to a set of QoS activity rules 530 using varioustechniques described herein. At 530, activity rules (e.g., activitypolicy rules instructions) 530 are determined using the mapping function520.

In some embodiments, the service plan includes a list of activitypolicies, and Each activity policy in the service plan specifies how theactivity policy is modified by rules state information. In someembodiments, each activity policy then becomes the instruction for theengine (e.g., QoS mapping function 520) that maps the activity policy toQoS activity rules 530. In some embodiments, service controller 122downloads QoS mapping function 520, which is implemented by serviceprocessor 115.

In some embodiments, the service processor determines (e.g., andclassifies) application/service usage activity demand with or withoutgranular application/service usage activity (e.g., depending on varioususer/service plan/service provider/network/legal and/or other privacyrestrictions and/or any other related requirements or settings). Forexample, policies (e.g., service policy settings and/or service profilesettings) can be downloaded to provide such application/service usageactivity monitoring rules and a QoS activity map for assigning suchmonitored activities to various QoS classes or priorities, and, in someembodiments, such monitoring and the QoS activity map can also beimplemented using various verification techniques described herein(e.g., periodically audited, tested, compared with network service usageinformation). In some embodiments, the QoS activity map is based on aservice plan, service profile, and/or service policy settings associatedwith the communications device. In some embodiments, the QoS activitymap is based on a device group and/or user group. In some embodiments,the QoS activity map is based on user input (e.g., a user of thecommunications device can identify QoS classes/service levels forvarious applications and/or service activities, in response to requestsfor user input, based on user configurations, user defined rules (e.g.,to eliminate or mitigate privacy and/or net neutrality concerns/issues),and/or confirmed monitored user behavior QoS related patterns orpreferences). In some embodiments, the QoS activity map includesmappings/associations based on one or more of the following: a userpreference for a given destination, destination class, application,application class (e.g., by application class instead of with respect toa specific application can also eliminate or mitigate privacy and/or netneutrality concerns/issues), flow, traffic or flow class, time period,time of day, location, network busy state (e.g., provide QoS when youcan, then charge more when busy, notify user of busy state), devicetype, user type, user plan, user group, user standing, partner service,tokens, service type, and/or other criteria or measures.

In some embodiments, various techniques described herein are managed fordevice 100 for incoming and/or outgoing QoS requests. In someembodiments, as shown in FIG. 6, QoS for DAS includes establishing anend to end coordinated QoS service channel control.

FIG. 6 illustrates a functional diagram for quality of service (QoS) fordevice assisted services for an end to end coordinated QoS servicechannel control in accordance with some embodiments. As shown in FIG. 6,a wireless communications device 100A includes a service processor 115Ain secure communication with service controller 122A. A wirelesscommunications device 100B includes a service processor 115B in securecommunication with service controller 122B. In some embodiments, when,for example, device 100A initiates a QoS request for a QoS class sessionin communication with device 100B (e.g., a VOIP call or anotherapplication service requiring or possibly using a QoS class/levelsession, such as a conversational or other QoS type of class/level), assequence of actions are performed using service controller 122A andservice controller 122B to facilitate/setup an end to end coordinatedQoS service channel control. In some embodiments, as similarly describedherein, assuming that service processor 115A and service controller 122Adetermine that the QoS request from device 100A is authorized for thatdevice, then the service controller 122A contacts registry 650 (e.g., adevice registry, such as an HLR, mobile services center, or othercentral database or registry including, for example, service controllermappings by device/IP address/other) to determine the service controllerassociated with/responsible for managing QoS/service control for device100B. The registry 650 provides the service controller 122B information(e.g., IP address/other address) based on this lookup determination. Insome embodiments, service controller 122A then initiates the QoS requestwith service controller 122B to determine if the device 100B isauthorized and/or available for the QoS session requested by device100A. In some embodiments, service controllers 122A and 122B communicatewith BTSs 125A/B to determine whether the QoS request can be facilitated(e.g., based on network capacity) as similarly described herein. In someembodiments, the service controllers 122A and 122B provide the centralQoS coordination function and can request appropriate QoS channelsdirectly from the respective local BTSs. In some embodiments, theservice controllers 122A and 122B also communicate with one or more ofthe following network elements/functions as shown in FIG. 6 in order tofacilitate an end to end coordinated QoS service channel control: RAN610/670, Core Network 620/660, and IPX network 630. In some embodiments,service controllers 122A and 122B communicate with various necessarynetwork elements for provisioning to facilitate session provisioningthrough the carrier core network as similarly discussed above. In someembodiments, service controllers 122A and 122B communicate with variousnecessary network elements for provisioning to facilitate sessionprovisioning through the IPX network as similarly discussed above. Aswill be apparent to one of ordinary skill in the art, QoS for DAStechniques as described herein can be similarly implemented using theseor similar techniques to various other network architectures.

FIG. 7 illustrates a flow diagram for quality of service (QoS) fordevice assisted services (DAS) in accordance with some embodiments. At702, the process begins. At 704, QoS rules are received or determined(e.g., a service processor receives or requests the QoS rules, which maybe included in service plan, service profile, and/or service policysettings associated with the communications device). In someembodiments, the QoS rules are verified using various techniques asdescribed herein (e.g., periodically updated, replaced, downloaded,obfuscated, and/or tested using by a service controller and/or usingother verification techniques). In some embodiments, a QoS API is alsoused by various applications to initiate a QoS request, as describedherein with respect to various embodiments. In some embodiments, the QoSrules are implemented in the form of a QoS activity map in accordancewith various embodiments described herein. At 706, the communicationsdevice's standing for QoS is determined using various techniquesdescribed herein (e.g., based on the service plan, service profile,service policy settings, QoS rules, based on QoS class, current serviceusage, current billing standing, and/or any other criteria/measure). Insome embodiments, in addition to verifying the device/user standing forthe QoS request, whether the device is following or in compliance withan assigned QoS reservation request policy is also verified usingvarious techniques described herein. If the device is determined to notbe eligible for QoS, then at 708, the device User Interface (UI)provides information concerning the denial/ineligibility for QoSsession(s) (e.g., denial/ineligibility explanation and/or options forproviding for one or more QoS options, such as a service plan upgrade orpayment for a certain/set of/period of time for QoS session(s) access).If the device is determined to be eligible for QoS, then at 710, QoSavailability is determined (e.g., based on network capacity, which maybe determined at the device, via communication with the servicecontroller, via communication with the BTS, and/or any combinationthereof, using the various techniques described herein). If QoS isdetermined to not be available, then at 712, the UI provides informationand/or options concerning the QoS availability (e.g., unavailabilityexplanation and/or options for providing for one or more QoS options,such as a service plan upgrade or payment for a certain/set of/period oftime for QoS session(s) access). If QoS is determined to be available,then at 714, a request for network resources for the QoS session is sentto one or more network resources (e.g., service controller, BTS,gateway, core/transport network, IPX/GRX networks, and/or other networkelements/functions/resources). At 716, a confirmation of the approvedQoS session is received to close the loop for the QoS for DAS (e.g., aQoS schedule is received that provides the QoS session confirmationinformation, such as a scheduled RAB/multi-RAB and/or other reservednetwork resource(s) by schedule/other criteria). At 718, one or moreverification techniques are performed to verify the QoS for DASimplementation on the device using various verification techniquesdescribed herein (e.g., comparing QoS service usage reports from anetwork source with the associated device policy; comparing QoS serviceusage reports from a network source with the QoS service usage reportsfrom the device, and/or using other verification techniques as similarlydescribed herein). At 720, the process is completed.

FIG. 8A through 8C each illustrates another flow diagram for quality ofservice (QoS) for device assisted services (DAS) in accordance with someembodiments. FIG. 8A illustrates another flow diagram for quality ofservice (QoS) for device assisted services (DAS) in accordance with someembodiments. At 802, the process begins. In some embodiments, the QoSpolicies are implemented on the device (e.g., service processorcollects/receives an associated service plan that defines/specifiesbasic policies for QoS, which can include a QoS activity map, which, forexample, maps QoS classes based on application, service usage, flowtype, destination, time of day, network capacity, and/or othercriteria/measures, as similarly described herein). In some embodiments,a QoS API is also used by various applications to initiate a QoSrequest, as described herein with respect to various embodiments. Insome embodiments, the QoS rules are implemented in the form of averified QoS activity map in accordance with various embodimentsdescribed herein. At 804, a QoS request is determined (e.g., by QoSclass for a particular associated service/application). In someembodiments, the QoS request is determined at least in part by using theQoS activity map using various techniques described herein, for example,based on service/application usage monitoring on the device (e.g., bythe service processor service usage monitoring agent). In someembodiments, the QoS request is determined based on the QoS API. In someembodiments, the QoS request is determined to be associated with anoutgoing connection or an incoming connection. At 806, whether the QoSrequest is authorized is determined (e.g., whether the QoS requestsupported by the service plan, sufficient charging credit exists forthis QoS request, and/or other criteria/measures). If not, then at 808,the UI provides a responsive notification and/or option as similarlydescribed herein. If the QoS request is approved, then at 810, a requestfor network resources for the QoS session is sent to one or more networkresources (e.g., service controller, BTS, gateway, core/transportnetwork, IPX/GRX networks, a/another service controller in communicationwith another communications device such as for setting up aconversational class QoS connection with the other communicationsdevice, and/or other network elements/functions/resources). If thedevice is determined to be eligible for QoS, then at 810, QoSavailability is determined (e.g., based on network capacity, which maybe determined at the device, via communication with the servicecontroller, via communication with the BTS, and/or any combinationthereof, using the various techniques described herein). If QoS isdetermined to not be available, then at 812, the UI provides informationand/or options concerning the QoS availability (e.g., unavailabilityexplanation and/or options for providing for one or more QoS options,such as a service plan upgrade or payment for a certain/set of/period oftime for QoS session(s) access). If QoS is determined to be available,then at 814, a request for network resources for the QoS session is sentto one or more network resources (e.g., service controller, BTS,gateway, core/transport network, IPX/GRX networks, and/or other networkelements/functions/resources, to setup, for example, a QoS end to endconnection—coordinate all resources end to end for the approved andverified QoS flow). At 816, a confirmation of the approved QoS sessionis received to close the loop for the QoS for DAS (e.g., a QoS scheduleis received that provides the QoS session confirmation information, suchas a scheduled RAB/multi-RAB and/or other reserved network resource(s)by schedule/other criteria). At 818, a QoS router is executed/performedon the communications device to assist in implementing QoS for DAS usingvarious verification techniques described herein (e.g., to perform QoSqueuing, throttling, and/or other QoS router related functions asdescribed herein). At 820, verified QoS charging is performed (e.g., atleast in part) on the device using various techniques described herein(e.g., using the service processor, such as the charging/service usagemonitoring and/or other agents as described herein). In someembodiments, QoS charging records and/or reports are provided to one ormore network elements for managing QoS billing and/or other QoSmanagement/billing related service control functions (e.g., to theservice controller and/or the billing interface or billing server). Insome embodiments, QoS for DAS also facilitates reestablishing the QoSsession/connection/channel/stream if the QoSsession/connection/channel/stream is lost or goes down, using similartechniques to those described herein as would be apparent to one ofordinary skill in the art. At 822, the process is completed. In someembodiments, the QoS provisioning channel is closed when the devicesession is over to, for example, free up various resources.

FIG. 8B illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.In some embodiments, QoS for DAS includes identifying the QoSrequirements (e.g., QoS level or QoS class) for a service activity. At824, the process begins. In some embodiments, the QoS policies areimplemented on the device (e.g., service processor collects/receives anassociated service plan that defines/specifies basic policies for QoS,which can include a QoS activity map, which, for example, maps QoSclasses based on application, service usage, flow type, destination,time of day, network capacity, and/or other criteria/measures, assimilarly described herein). In some embodiments, the QoS rules areimplemented in the form of a verified QoS activity map in accordancewith various embodiments described herein. At 826, the device monitorsdevice activity, such as service/application usage activities. In someembodiments, the device detects the relevant activities based on variousservice usage monitoring techniques described herein. At 828, a QoSrequest is determined, for example, using various techniques describedherein. At 830, a QoS level is determined based on the applicationassociated with the QoS request using various techniques describedherein. For example, the QoS level can be determined using the QoSactivity map, which provides a QoS policy defined by a table associatingvarious QoS levels with a variety of activities that include variousdevice monitored service usage/application activities. In someembodiments, the QoS activity map includes QoS level mappings based onone or more of the following: application, destination/source, traffictype, connection type, content type, time of day/day of week, networkcapacity, activity usage, service plan selection, current standing, userclass, device class, home/roaming, network capabilities, and/or othercriteria/measures as similarly described herein. In some embodiments, at832, if the QoS level cannot be determined and/or in order to confirm aQoS level or selection among multiple potential appropriate/approved QoSlevels, the UI presents options for a user to select the QoS level. At834, the QoS request is initiated for the determined QoS level (e.g.,QoS class). At 836, the process is completed.

FIG. 8C illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.In some embodiments, QoS for DAS includes determining whether thenetwork should grant the QoS request for a given device activity. At842, the process begins. At 844, QoS request is determined. At 846, thecommunications device's standing for QoS is determined using varioustechniques described herein (e.g., a service processor in combinationwith a service controller or based on a communication for authorizationof the QoS request sent to the service controller determines whether theQoS request is authorized, which can be based on the service plan,service profile, service policy settings, QoS rules, based on QoS class,current service usage, current billing standing, and/or any othercriteria/measure). If the device is determined to not be eligible forQoS, then at 848, the device User Interface (UI) provides informationconcerning the denial/ineligibility for QoS session(s) (e.g.,denial/ineligibility explanation and/or options for providing for one ormore QoS options, such as a service plan upgrade or payment for acertain/set of/period of time for QoS session(s) access). If the deviceis determined to be eligible for QoS, then at 850, QoS availability isdetermined (e.g., based on network capacity, which may be determined atthe device, via communication with the service controller, viacommunication with the BTS, and/or any combination thereof, using thevarious techniques described herein). If QoS is determined to not beavailable, then at 852, the UI provides information and/or optionsconcerning the QoS availability (e.g., unavailability explanation and/oroptions for providing for one or more QoS options, such as a serviceplan upgrade or payment for a certain/set of/period of time for QoSsession(s) access). If QoS is determined to be available, then at 854, arequest for network resources for the QoS session is sent to one or morenetwork resources (e.g., service controller, BTS, gateway,core/transport network, IPX/GRX networks, and/or other networkelements/functions/resources can be queried directly and/or acentralized QoS resource/network function/element/database can bequeried for determining such network resources and coordinating suchscheduling). At 856, a confirmation of the approved QoS session isreceived to close the loop for the QoS for DAS (e.g., a QoS schedule isreceived that provides the QoS session confirmation information, such asa scheduled RAB/multi-RAB and/or other reserved network resource(s) byschedule/other criteria). At 858, a QoS router is performed. In someembodiments, the QoS router is performed on the device (e.g., serviceprocessor), on a network element/function (e.g., service controller),and/or in combinations thereof. In some embodiments, the QoS routerprioritizes multiple QoS requests across a given communications device.In some embodiments, the QoS router prioritizes multiple QoS requestsacross multiple communications devices and/or across multiple BTSs. Insome embodiments, the QoS router performs various QoS class degradation,promotion, and/or other throttling related techniques as similarlydescribed herein (e.g., based on session priority, network capacity,workload balancing, QoS priority rules, and/or othercriteria/measures/rules). At 860, the process is completed.

FIG. 9 illustrates another flow diagram for quality of service (QoS) fordevice assisted services (DAS) in accordance with some embodiments. Insome embodiments, QoS for DAS includes QoS session provision for aservice activity. At 902, the process begins. At 904, a new QoS sessionis granted and/or confirmed. At 906, a device service processor (e.g.,policy decision point (PDP) agent, also referred to herein as a policycontrol agent) maps the QoS session grant to a QoS monitoring policy(e.g., based on a service controller provided QoS related policy, basedon a service plan associated with the device, user, device/user group,and/or other criteria/measures, as similarly described herein). At 908,the QoS monitoring policy provides commands/instructions to a policyenforcement point (PEP) (e.g., PEP agent, also referred to herein as apolicy implementation agent) for managing/enforcing the new QoSpriorities/sessions. At 910, the PEP determines whether to allow, block,throttle, and/or queue priority a session based on the QoS monitoringpolicy. At 912, the process is completed.

FIG. 10 illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.In some embodiments, Radio Access Bearer (RAB) support is available, andthe following process is performed in accordance with some embodiments.At 1002, the process begins. At 1004, the device service processordetects a QoS request or QoS need (e.g., a QoS API request, a QoSrequest or need/benefit of QoS session based on service usagemonitoring, such as by application, or other service usagemeasure/activity). At 1006, the service processor and/or the serviceprocessor in communication with the service controller determines if theservice plan allows/supports the requested QoS. If not, then at 1008, aUI event is generated (e.g., notifying the device user that such QoS/QoSlevel/class is not available, and potentially offering a QoS/serviceplan upgrade/purchase for that QoS/QoS level/class). At 1010, theservice processor communicates the QoS request to the service controller(e.g., using a secure service control link or secure communicationchannel, as similarly described herein) to request the QoS level/class.At 1012, the service controller determines whether network resources areavailable using various techniques as described herein. In someembodiments, network capacity is determined using various techniques,such as local device measurements; dedicated local device measurementreports; BTS reports; other network element reports; by assessing, forexample, a combination of one or more of available bandwidth, trafficdelay or latency, available QoS level, variability in availablebandwidth, variability in latency, and/or variability in available QoSlevel; and/or other techniques as described herein. At 1014, the servicecontroller responds to the QoS request (e.g., grants or denies the QoSrequest). In some embodiments, another UI event is generated if the QoSrequest is denied as similarly described herein. At 1016 (assuming theQoS request is granted), the device requests a QoS channel from the BTS.In some embodiments, the request includes a QoS request authorizationcode received from the service controller. In some embodiments, theservice controller provides a notification of the QoS request approvalfor the communications device to the BTS, so that the BTS can verify theapproval of the QoS request. In some embodiments, the BTS confirms thedevice QoS channel request directly with the service controller. Forexample, various other techniques for verifying the QoS channel requestcan also be used as similarly described herein and as would be apparentto one of ordinary skill in the art. In some embodiments, the deviceservice processor and/or service controller provides QoS related reportsinforming the BTS of how many QoS channels (e.g., RABs) to provision andhow many best effort resources to provision based on device demandprojections. At 1018 (assuming the QoS channel request is verified), theQoS session is initiated based on an allocated RAB or multi-RABreservation received from the BTS (e.g., and/or other network elementsas similarly described herein). At 1020, the process is completed.

FIG. 11 illustrates another flow diagram for quality of service (QoS)for device assisted services (DAS) in accordance with some embodiments.In some embodiments, RAB support is not available, and the followingprocess is performed in accordance with some embodiments. At 1102, theprocess begins. At 1104, the device service processor detects a QoSrequest or QoS need (e.g., a QoS API request, a QoS request orneed/benefit of QoS session based on service usage monitoring, such asby application, or other service usage measure/activity). At 1106, theservice processor and/or the service processor in communication with theservice controller determines if the service plan allows/supports therequested QoS. If not, then at 1108, a UI event is generated (e.g.,notifying the device user that such QoS/QoS level/class is notavailable, and potentially offering a QoS/service plan upgrade/purchasefor that QoS/QoS level/class). At 1110, the service processorcommunicates the QoS request to the service controller (e.g., using asecure service control link or secure communication channel, assimilarly described herein) to request the QoS level/class. At 1112, theservice controller determines whether network resources are availableusing various techniques as described herein. In some embodiments,network capacity is determined using various techniques, such as localdevice measurements, BTS reports, other network element reports, and/orother techniques as described herein. In some embodiments, the servicecontroller throttles other devices on the link so that the requested QoSlevel can be achieved (e.g., as RAB support is not available). In someembodiments, the service controller time slots traffic from the deviceend in synchronization with a BTS clock or absolute clock to facilitatethe requested QoS level and to achieve necessary network capacity tosupport/facilitate the requested QoS level (e.g., minimizingjitter/inter-packet delay variation) based on current/forecasted networkcapacity on the link. At 1114, the service controller responds to theQoS request (e.g., grants or denies the QoS request). In someembodiments, another UI event is generated if the QoS request is deniedas similarly described herein. At 1116 (assuming the QoS request isgranted), the device initiates the QoS session. At 1118, the deviceservice processor and/or the device service processor in securecommunication with the service controller monitors and verifies the QoSsession using various monitoring and verification techniques describedherein (e.g., checks CDRs to determine if the QoS channel is properlyimplemented by the device). In some embodiments, a UI event is generatedto notify the device user if there are potential problems with the QoSsession implementation, to periodically inform the user of QoS charging,and/or other events/information related to QoS activities. At 1120, theprocess is completed.

FIG. 12 illustrates a device stack for providing various service usagemeasurement techniques in accordance with some embodiments. FIG. 12illustrates a device stack providing various service usage measurementfrom various points in the networking stack for a service monitor agent(e.g., for monitoring QoS related activities as described herein), abilling agent, and an access control integrity agent to assist inverifying the service usage measures, QoS related activities andfunctions, and billing reports in accordance with some embodiments. Asshown in FIG. 12, several service agents take part in data pathoperations to achieve various data path improvements, and, for example,several other service agents can manage the policy settings for the datapath service, implement billing for the data path service, manage one ormore modem selection and settings for access network connection,interface with the user and/or provide service policy implementationverification. Additionally, in some embodiments, several agents performfunctions to assist in verifying that the service control or monitoringpolicies intended to be in place are properly implemented, the servicecontrol or monitoring policies are being properly adhered to, that theservice processor or one or more service agents are operating properly,to prevent unintended errors in policy implementation or control, and/orto prevent tampering with the service policies or control. As shown, theservice measurement points labeled I through VI represent variousservice measurement points for service monitor agent 1696 and/or otheragents to perform various service monitoring activities. Each of thesemeasurement points can have a useful purpose in various embodimentsdescribed herein. For example, each of the traffic measurement pointsthat is employed in a given design can be used by a monitoring agent totrack application layer traffic through the communication stack toassist policy implementation functions, such as the policyimplementation driver/agent 1690 (e.g., policy enforcement pointdriver/agent), or in some embodiments the modem firewall agent 1655 orthe application interface agent, in making a determination regarding thetraffic parameters or type once the traffic is farther down in thecommunication stack where it is sometimes difficult or impossible tomake a complete determination of traffic parameters. The particularlocations for the measurement points provided in these figures areintended as instructional examples, and other measurement points can beused for different embodiments, as will be apparent to one of ordinaryskill in the art in view of the embodiments described herein. Generally,in some embodiments, one or more measurement points within the devicecan be used to assist in service control verification and/or device orservice troubleshooting.

In some embodiments, the service monitor agent and/or other agentsimplement virtual traffic tagging by tracking or tracing packet flowsthrough the various communication stack formatting, processing andencryption steps, and providing the virtual tag information to thevarious agents that monitor, control, shape, throttle or otherwiseobserve, manipulate or modify the traffic. This tagging approach isreferred to herein as virtual tagging, because there is not a literaldata flow, traffic flow or packet tag that is attached to flows orpackets, and the book-keeping to tag the packet is done through trackingor tracing the flow or packet through the stack instead. In someembodiments, the application interface and/or other agents identify atraffic flow, associate it with a service usage activity and cause aliteral tag to be attached to the traffic or packets associated with theactivity. This tagging approach is referred to herein as literaltagging. There are various advantages with both the virtual tagging andthe literal tagging approaches. For example, it can be preferable insome embodiments to reduce the inter-agent communication required totrack or trace a packet through the stack processing by assigning aliteral tag so that each flow or packet has its own activity associationembedded in the data. As another example, it can be preferable in someembodiments to re-use portions of standard communication stack softwareor components, enhancing the verifiable traffic control or servicecontrol capabilities of the standard stack by inserting additionalprocessing steps associated with the various service agents andmonitoring points rather than re-writing the entire stack to correctlyprocess literal tagging information, and in such cases, a virtualtagging scheme may be desired. As yet another example, some standardcommunication stacks provide for unused, unspecified or otherwiseavailable bit fields in a packet frame or flow, and these unused,unspecified or otherwise available bit fields can be used to literallytag traffic without the need to re-write all of the standardcommunication stack software, with only the portions of the stack thatare added to enhance the verifiable traffic control or service controlcapabilities of the standard stack needing to decode and use the literaltagging information encapsulated in the available bit fields. In thecase of literal tagging, in some embodiments, the tags are removed priorto passing the packets or flows to the network or to the applicationsutilizing the stack. In some embodiments, the manner in which thevirtual or literal tagging is implemented can be developed into acommunication standard specification so that various device or serviceproduct developers can independently develop the communication stackand/or service processor hardware and/or software in a manner that iscompatible with the service controller specifications and the productsof other device or service product developers.

It will be appreciated that although the implementation/use of any orall of the measurement points illustrated in FIG. 12 is not required tohave an effective implementation, such as was similarly shown withrespect to various embodiments described herein, various embodiments canbenefit from these and/or similar measurement points. It will also beappreciated that the exact measurement points can be moved to differentlocations in the traffic processing stack, just as the variousembodiments described herein can have the agents affecting policyimplementation moved to different points in the traffic processing stackwhile still maintaining effective operation. In some embodiments, one ormore measurement points are provided deeper in the modem stack where,for example, it is more difficult to circumvent and can be moredifficult to access for tampering purposes if the modem is designed withthe proper software and/or hardware security to protect the integrity ofthe modem stack and measurement point(s).

Referring to FIG. 12, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for each of the modems of thedevice at the bottom of the device communications stack. Examplemeasurement point VI resides within or just above the modem driverlayer. For example, the modem driver performs modem bus communications,data protocol translations, modem control and configuration to interfacethe networking stack traffic to the modem. As shown, measurement pointVI is common to all modem drivers and modems, and it is advantageous forcertain embodiments to differentiate the traffic or service activitytaking place through one modem from that of one or more of the othermodems. In some embodiments, measurement point VI, or anothermeasurement point, is located over, within or below one or more of theindividual modem drivers. The respective modem buses for each modemreside between example measurement points V and VI. In the next higherlayer, a modem selection & control layer for multimode device basedcommunication is provided. In some embodiments, this layer is controlledby a network decision policy that selects the most desirable networkmodem for some or all of the data traffic, and when the most desirablenetwork is not available the policy reverts to the next most desirablenetwork until a connection is established provided that one of thenetworks is available. In some embodiments, certain network traffic,such as verification, control, redundant or secure traffic, is routed toone of the networks even when some or all of the data traffic is routedto another network. This dual routing capability provides for a varietyof enhanced security, enhanced reliability or enhanced manageabilitydevices, services or applications. In the next higher layer, a modemfirewall is provided. For example, the modem firewall provides fortraditional firewall functions, but unlike traditional firewalls, inorder to rely on the firewall for verifiable service usage control, suchas access control and security protection from unwanted networkingtraffic or applications, the various service verification techniques andagents described herein are added to the firewall function to verifycompliance with service policy and prevent tampering of the servicecontrols. In some embodiments, the modem firewall is implemented fartherup the stack, possibly in combination with other layers as indicated inother Figures and described herein. In some embodiments, a dedicatedfirewall function or layer is provided that is independent of the otherprocessing layers, such as the policy implementation layer, the packetforwarding layer and/or the application layer. In some embodiments, themodem firewall is implemented farther down the stack, such as within themodem drivers, below the modem drivers, or in the modem itself. Examplemeasurement point IV resides between the modem firewall layer and an IPqueuing and routing layer (e.g., QoS IP queuing and routing layer). Asshown, an IP queuing and routing layer is separate from the policyimplementation layer where the policy implementation agent implements aportion of the traffic control and/or service usage control policies. Asdescribed herein, in some embodiments, these functions are separated sothat a standard network stack function can be used for QoS IP queuingand routing, and the modifications necessary to implement the policyimplementation agent functions can be provided in a new layer insertedinto the standard stack. In some embodiments, the IP queuing and routinglayer is combined with the traffic or service usage control layer. Forexample, a combined routing and policy implementation layer embodimentcan also be used with the other embodiments, such as shown in FIG. 12.Measurement point III resides between the IP queuing and routing layerand a policy implementation agent layer. Measurement point II residesbetween the policy implementation agent layer and the transport layer,including TCP, UDP, and other IP as shown. The session layer residesabove the transport layer, which is shown as a socket assignment andsession management (e.g., basic TCP setup, TLS/SSL) layer. The networkservices API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP(Simple Mail Transfer Protocol), POP3, DNS) resides above the sessionlayer. Measurement point I resides between the network services APIlayer and an application layer, shown as application service interfaceagent in the device communications stack of FIG. 12.

As shown in FIG. 12, the application service interface layer (e.g., QoSapplication service interface layer) is above the standard networkingstack API and, in some embodiments, its function is to monitor and insome cases intercept and process the traffic between the applicationsand the standard networking stack API. In some embodiments, theapplication service interface layer identifies application traffic flowsbefore the application traffic flows are more difficult or practicallyimpossible to identify farther down in the stack. In some embodiments,the application service interface layer in this way assists applicationlayer tagging in both the virtual and literal tagging cases. In the caseof upstream traffic, the application layer tagging is straight forward,because the traffic originates at the application layer. In somedownstream embodiments, where the traffic or service activityclassification relies on traffic attributes that are readily obtainable,such as source address or URL, application socket address, IPdestination address, time of day or any other readily obtainedparameter, the traffic type can be identified and tagged for processingby the firewall agent or another agent as it initially arrives. In otherembodiments, as described herein, in the downstream case, the solutionis generally more sophisticated when a traffic parameter that is neededto classify the manner in which the traffic flow is to be controlled orthrottled is not readily available at the lower levels of the stack,such as association with an aspect of an application, type of content,something contained within TLS, IPSEC or other secure format, or otherinformation associated with the traffic. Accordingly, in someembodiments the networking stack identifies the traffic flow before itis fully characterized, categorized or associated with a serviceactivity, and then passes the traffic through to the applicationinterface layer where the final classification is completed. In suchembodiments, the application interface layer then communicates thetraffic flow ID with the proper classification so that after an initialshort traffic burst or time period the policy implementation agents canproperly control the traffic. In some embodiments, there is also apolicy for tagging and setting service control policies for traffic thatcannot be fully identified with all sources of tagging includingapplication layer tagging.

As shown in FIG. 12, a service monitor agent, which is also incommunication with the agent communication bus 1630, communicates withvarious layers of the device communications stack. For example, theservice monitor agent, performs monitoring at each of measurement pointsI through VI, receiving information including application information,service usage and other service related information, and assignmentinformation. An access control integrity agent is in communication withthe service monitor agent via the agent communications bus 1630, as alsoshown.

FIG. 13 illustrates another device stack for providing various serviceusage measurement techniques in accordance with some embodiments. FIG.13 illustrates an embodiment similar to FIG. 12 in which some of theservice processor is implemented on the modem and some of the serviceprocessor is implemented on the device application processor inaccordance with some embodiments. In some embodiments, a portion of theservice processor is implemented on the modem (e.g., on modem modulehardware or modem chipset) and a portion of the service processor isimplemented on the device application processor subsystem. It will beapparent to one of ordinary skill in the art that variations of theembodiment depicted in FIG. 13 are possible where more or less of theservice processor functionality is moved onto the modem subsystem oronto the device application processor subsystem. For example, suchembodiments similar to that depicted in FIG. 13 can be motivated by theadvantages of including some or all of the service processor networkcommunication stack processing and/or some or all of the other serviceagent functions on the modem subsystem (e.g., and such an approach canbe applied to one or more modems). For example, the service processorcan be distributed as a standard feature set contained in a modemchipset hardware of software package or modem module hardware orsoftware package, and such a configuration can provide for easieradoption or development by device OEMs, a higher level ofdifferentiation for the chipset or modem module manufacturer, higherlevels of performance or service usage control implementation integrityor security, specification or interoperability standardization, and/orother benefits.

Referring to FIG. 13, describing the device communications stack fromthe bottom to the top of the stack as shown, the device communicationsstack provides a communication layer for modem MAC/PHY layer at thebottom of the device communications stack. Measurement point IV residesabove the modem MAC/PHY layer. The modem firewall layer resides betweenmeasurement points IV and III. In the next higher layer, the policyimplementation agent is provided, in which the policy implementationagent is implemented on the modem (e.g., on modem hardware). Measurementpoint II resides between the policy implementation agent and the modemdriver layer, which is then shown below a modem bus layer. The nexthigher layer is shown as the IP queuing and routing layer, followed bythe transport layer, including TCP, UDP, and other IP as shown. Thesession layer resides above the transport layer, which is shown as asocket assignment and session management (e.g., basic TCP setup,TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (FileTransfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS)resides above the session layer. Measurement point I resides between thenetwork services API layer and an application layer, shown asapplication service interface agent in the device communications stackof FIG. 13.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

1. A system, comprising: one or more modems for enabling a wireless enduser communications device to communicate at least over a first wirelessaccess network and a second wireless access network; a processor of thewireless end user communications device configured to: determine thatthe wireless end user communications device is connected to the firstwireless access network; when the wireless end user communicationsdevice is connected to the first wireless access network: facilitate aplurality of simultaneous quality-of-service (QoS) connections betweenthe wireless end user communications device and a network systemcommunicatively coupled to the wireless end user communications deviceby the first wireless access network, associate a particular serviceactivity of the wireless end user communications device with aparticular QoS connection of the plurality of simultaneous QoSconnections, and assist in implementing a first traffic controlconfigured to control attempted or successful communications associatedwith the particular service activity over the particular QoS connection;and when the wireless end user communications device is connected to thesecond wireless access network, assist in implementing a second trafficcontrol configured to control attempted or successful communicationsassociated with the particular service activity, the second trafficcontrol being different from the first traffic control; and memorycoupled to the processor and configured to provide the processor withinstructions.
 2. The system recited in claim 1, wherein the particularQoS connection supports a first QoS level, wherein the first QoS levelcomprises one or more of conversational, streaming, interactive data,best-effort data, and background data, and wherein a second QoSconnection of the plurality of simultaneous QoS connections supports asecond QoS level that is not supported by the particular QoS connection.3. The system recited in claim 1, wherein associate a particular serviceactivity of the wireless end user communications device with aparticular QoS connection of the plurality of simultaneous QoSconnections comprises: obtain a QoS request through a QoS applicationprogramming interface (API), the QoS API comprising an interface on thewireless end user communications device configured to communicate QoSinformation to or from an application on the wireless end usercommunications device.
 4. The system recited in claim 1, wherein theprocessor is configured to associate the particular service activitywith the particular QoS connection at least in part by monitoringattempted or successful communications by the wireless end usercommunications device associated with the particular service activity.5. The system recited in claim 1, wherein the processor is configured toassociate the particular service activity with the particular QoSconnection based at least in part on one or more of the following: anapplication activity, a network end point or destination, a traffictype, a content type, and a pattern of application or QoS serviceactivity.
 6. The system recited in claim 1, wherein the processor isfurther configured to: assist in providing a user notificationassociated with the particular service activity, wherein the usernotification includes one or more of the following: a confirmation of aQoS request or a QoS communication attempt associated with theparticular service activity, a confirmation for future similar QoSrequests or similar QoS communication attempts associated with theparticular service activity, an indication that a first QoS levelassociated with the QoS request or the QoS communication attempt will beprovided, an indication that the first QoS level is not available orwill not be provided, an option to purchase a service level associatedwith the QoS request or the QoS communication attempt, an option toupgrade to a new service plan, and an indication that the particularservice activity requires or can benefit from a second QoS level.
 7. Thesystem recited in claim 1, wherein the processor is further configuredto: assist in implementing a service profile for assisting in the firsttraffic control of the particular service activity, wherein the serviceprofile includes one or more service policy settings for assisting inmonitoring the attempted or successful communications associated withthe particular service activity based on the service profile; and updatethe service profile based on information obtained from a network elementor from a service controller.
 8. The system recited in claim 1, whereinthe processor is further configured to: determine if the particularservice activity is authorized for the particular QoS connection basedon a service plan associated with the wireless end user communicationsdevice, or based on a user input; and when the particular serviceactivity is not authorized for the particular QoS connection, preventthe particular service activity from using the particular QoSconnection.
 9. The system recited in claim 1, wherein the processor isconfigured to associate the particular service activity with theparticular QoS connection of the plurality of simultaneous QoSconnections at least in part by determining if a QoS request or QoScommunication attempt associated with the particular service activity isauthorized based on QoS rules.
 10. The system recited in claim 1,wherein associate a particular service activity of the wireless end usercommunications device with a particular QoS connection of the pluralityof simultaneous QoS connections comprises: obtain at least an aspect ofQoS rules from a service controller or a network element, determine if aQoS request or QoS communication attempt associated with the particularservice activity is allowed based at least in part on the obtainedaspect of the QoS rules; and take an action based on the determination.11. The system recited in claim 1, wherein the processor is furtherconfigured to: obtain at least an aspect of QoS rules from a servicecontroller or a network element, wherein the QoS rules include a QoSactivity map that associates the particular service activity with one ormore QoS levels.
 12. The system recited in claim 1, wherein theprocessor is further configured to: determine if a QoS request or QoScommunication attempt associated with the particular service activity isauthorized; and assist in providing a user notification if the QoSrequest or QoS communication attempt is not authorized.
 13. The systemrecited in claim 1, wherein the processor is further configured to:determine whether a QoS request associated with the particular serviceactivity is authorized for the particular QoS connection based on QoSrules; and send the QoS request to an access point if the QoS request isdetermined to be authorized for the particular QoS connection based onthe QoS rules, wherein the access point assists the processor infacilitating the particular QoS connection.
 14. The system recited inclaim 1, wherein the processor is further configured to: send a firstQoS request associated with the particular service activity to a servicecontroller or a network element; receive a QoS approval authorizationfor the particular QoS connection of the plurality of simultaneous QoSconnections from the service controller or the network element; and senda second QoS request to a base station, wherein the second QoS requestincludes the QoS approval authorization.
 15. The system recited in claim1, wherein the processor is further configured to: send a QoS requestassociated with the particular service activity to a service controller,wherein the service controller assists the processor in facilitating theparticular QoS connection; and obtain a QoS reservation for theparticular QoS connection from the service controller.
 16. The systemrecited in claim 1, wherein the processor is further configured to:assist in determining an accounting for usage associated with theparticular service activity.
 17. The system recited in claim 1, whereinthe processor is further configured to assist in implementing the firsttraffic control at least in part by implementing a QoS router forassisting in managing one or more of the plurality of simultaneous QoSconnections.
 18. The system recited in claim 1, wherein the processor isfurther configured to: assist in sending network capacity information ornetwork congestion information to a network element or to a servicecontroller.
 19. The system recited in claim 17, wherein the QoS routeris configured to assist in implementing at least one of: upgrade a QoSclass or a QoS level, downgrade a QoS class or a QoS level, deallocate aQoS class or a QoS level, traffic shape a communication associated withone of the plurality of simultaneous QoS connections, delay acommunication associated with one of the plurality of simultaneous QoSconnections, time window a communication associated with one of theplurality of simultaneous QoS connections, throttle a communicationassociated with one of the plurality of simultaneous QoS connections,queue with priority a communication associated with one of the pluralityof simultaneous QoS connections, and block a communication associatedwith one of the plurality of simultaneous QoS connections based onwireless network QoS availability or congestion.
 20. The system recitedin claim 19, wherein the QoS router is configured to assist inimplementing one or more of the following: a background QoS servicelevel; a best effort service level, a QoS differentiated service level,and a QoS guaranteed service level.
 21. The system recited in claim 1,wherein the particular service activity is a first service activity, andwherein the particular QoS connection is a first QoS connectionassociated with a first QoS class, and wherein the processor is furtherconfigured to assist in passing, blocking, controlling, throttling,delaying, deferring, routing, directing, priority queuing, forwarding,or tunneling attempted or successful communications associated with asecond service activity over a second QoS connection of the plurality ofsimultaneous QoS connections, wherein the second QoS connection isassociated with a second QoS class.
 22. The system recited in claim 17,wherein the processor is further configured to obtain network QoSinformation from a network element, a base station or a servicecontroller, the network QoS information comprising one or more ofnetwork capacity information, network congestion information, QoSavailability information and a QoS policy, and wherein implementing theQoS router comprises using the received network QoS information.
 23. Thesystem recited in claim 17, wherein the processor is further configuredto: offer, to a user, a choice of whether to allow the QoS router todynamically manage QoS of one or more service activities available tothe wireless end user communications device.
 24. The system recited inclaim 1, wherein the processor is further configured to: assist indetermining a service usage accounting for the particular QoSconnection, wherein the service usage accounting is determined based atleast in part on one or more of the following: a QoS level, a QoS class,a traffic priority level, a network type, an allocated networkbandwidth, a QoS priority, and a radio access bearer (RAB) type.
 25. Amethod performed by one or more processors in a wireless end usercommunications device configured to communicate at least over a firstwireless access network and a second wireless access network, the methodcomprising: determining that the wireless end user communications deviceis connected to the first wireless access network; when the wireless enduser communications device is connected to the first wireless accessnetwork: facilitating a plurality of simultaneous quality-of-service(QoS) connections between the wireless end user communications deviceand a network system communicatively coupled to the wireless end usercommunications device by the first wireless access network; associatinga particular service activity of the wireless end user communicationsdevice with a particular QoS connection of the plurality of simultaneousQoS connections; and assisting in implementing a first traffic controlconfigured to control attempted or successful communications over theparticular QoS connection that is associated with the particular serviceactivity; and when the wireless end user communications device isconnected to the second wireless access network, assist in implementinga second traffic control configured to control attempted or successfulcommunications associated with the particular service activity over thesecond wireless access network, the second traffic control beingdifferent from the first traffic control.
 26. A computer programproduct, the computer program product being embodied in a non-transitorycomputer readable storage medium and comprising computer instructionsexecuted in one or more processors of a wireless end user communicationsdevice configured to communicate at least over a first wireless accessnetwork and a second wireless access network, the computer instructionsfor: determining that the wireless end user communications device isconnected to the first wireless access network; when the wireless enduser communications device is connected to the first wireless accessnetwork: facilitating a plurality of simultaneous quality-of-service(QoS) connections between the wireless end user communications deviceand a network system communicatively coupled to the wireless end usercommunications device by the first wireless access network; associatinga particular service activity of the wireless end user communicationsdevice with a particular QoS connection of the plurality of simultaneousQoS connections; and assisting in implementing a first traffic controlconfigured to control attempted or successful communications over theparticular QoS connection that is associated with the particular serviceactivity; and when the wireless end user communications device isconnected to the second wireless access network, assist in implementinga second traffic control configured to control attempted or successfulcommunications associated with the particular service activity over thesecond wireless access network, the second traffic control beingdifferent from the first traffic control.
 27. The system recited inclaim 9, wherein the QoS rules are associated with a service plan forthe wireless end user communications device.
 28. The system recited inclaim 9, wherein the processor of the wireless end user communicationsdevice is further configured to: assist in providing a user notificationthrough a user interface of the wireless end user communications device,the user notification describing an aspect of the QoS rules.
 29. Thesystem recited in claim 10, wherein the action comprises one or more of:assist to establish the particular QoS connection; assist to provide aQoS level; forward information about the QoS request or QoScommunication attempt to a network element or to a service controller;assist to deny the particular QoS connection; assist to deny the QoSlevel; decline to forward information about the QoS request or QoScommunication attempt to the network element or to the servicecontroller; and assist in providing a user interface notificationassociated with the QoS request or QoS communication attempt.
 30. Thesystem recited in claim 1, wherein the particular service activitycomprises an attempted or successful network access associated with oneor more of the following: an application, a network destination, anetwork source, a network end point, a uniform resource locator (URL), awebsite, a network server, a particular service provider, a particularnetwork type, a traffic type, a content type, a network protocol, atraffic session type, a QoS identifier, a time of day, a state ofnetwork capacity, a network busy state, a user service planauthorization or standing, a roaming or home network status,voice-over-Internet-protocol (VOIP) traffic, streaming video traffic,differentiated access bandwidth during busy network periods, real-timeinteractive traffic, communications that include network connectedmultimedia meetings, communications that include shared presentations,communications that include pictures, communications that includevideos, communications that include voice, Internet browsing, shortmessage service (SMS) or push to talk, email message body delivery,email attachment delivery, communications associated with backgrounddownload services, communications associated with email downloads orother file transfers, communications associated with file transferprotocol (FTP), communications taking place when the user is notinteracting with an application that is communicating with the network,communications associated with software updates, communicationsassociated with a best effort QoS level, communications associated withan interactive QoS level, communications associated with a QoS level fortime sensitive services, communications associated with a guaranteed bitrate QoS level, communications associated with a near real time orinteractive QoS level, and communications associated with a backgroundQoS level.
 31. The system recited in claim 1 wherein the particularservice activity comprises attempted or successful communicationsassociated with an application on the wireless end user communicationsdevice.
 32. The system recited in claim 11, wherein the one or more QoSlevels comprise a background service level, and wherein the processor isfurther configured to assist in implementing the first traffic controlby implementing a QoS policy associated with the background servicelevel.
 33. The system recited in claim 11, wherein the particularservice activity comprises attempted or successful communicationsassociated with an application on the wireless end user communicationsdevice, and wherein the one or more QoS levels comprise a backgroundservice level, and wherein the processor is further configured to assistin implementing a QoS policy associated with the background servicelevel.
 34. The system recited in claim 12, wherein the user notificationincludes one or more of the following: information about a denial of theQoS request or QoS communication attempt, information explaining areason for a denial of the QoS request or QoS communications attempt, anoption to purchase a new service level for the QoS request or QoScommunication attempt, and an option to upgrade to a new service plan.35. The system recited in claim 21, wherein the first QoS connection orthe second QoS connection is one or more of a prioritized traffic queue,a radio access bearer, a QoS channel, and a QoS session.
 36. The systemrecited in claim 17, wherein assisting in managing one or more of theplurality of simultaneous QoS connections comprises assisting inimplementing one or more traffic shaping parameters for the one or moreof the plurality of simultaneous QoS connections.
 37. The system recitedin claim 1, wherein associate a particular service activity of thewireless end user communications device with a particular QoS connectionof the plurality of simultaneous QoS connections comprises identify anattempted or successful traffic flow associated with a particular QoSlevel, the attempted or successful traffic flow comprising one or morerelated data transfers.
 38. The system recited in claim 37, whereinidentify the attempted or successful traffic flow comprises tag theattempted or successful flow to preserve an association between theattempted or successful traffic flow and an application on the wirelessend user communication device when the attempted or successful trafficflow is processed by one or more operations on the wireless end usercommunications device.
 39. The system recited in claim 37, whereinidentify the attempted or successful traffic flow comprises tag theattempted or successful traffic flow to preserve an association betweenthe attempted or successful traffic flow and a traffic type when theattempted or successful traffic flow is processed by one or moreoperations on the wireless end user communications device.
 40. Thesystem recited in claim 37, wherein identify the attempted or successfultraffic flow comprises tag the attempted or successful traffic flow topreserve an association between the attempted or successful traffic flowand a network endpoint or network destination when the attempted orsuccessful traffic flow is processed by one or more operations on thewireless end user communications device.
 41. The system recited in claim37, wherein identify the attempted or successful traffic flow comprisestag the attempted or successful traffic flow to preserve an associationbetween the attempted or successful traffic flow and a traffic route, atraffic re-direction, a traffic tunnel, the particular QoS connection, aradio access bearer, a QoS channel, a QoS session, or a logical channelwhen the attempted or successful traffic flow is processed by one ormore operations on the wireless end user communications device.
 42. Thesystem recited in claim 1, wherein the processor is further configuredto provide a QoS application programming interface (API), the QoS APIcomprising an interface on the wireless end user communications devicefor communicating QoS information to or from an application on thewireless end user communications device.
 43. The system recited in claim42, wherein the QoS information communicated to or from the applicationcomprises information to inform the application of at least one of anavailable QoS level, a level of network congestion, an available datarate, an available bandwidth, and an available communication performancelevel.
 44. The system recited in claim 42, wherein the QoS informationcommunicated to or from the application comprises information to informthe application of one or more networks to which the wireless end usercommunications device is connected or is capable of being connected. 45.The system recited in claim 42, wherein the QoS information communicatedto or from the application comprises information enabling theapplication to request or establish a level of QoS, a first QoSconnection of the plurality of simultaneous QoS connections, a QoSenabled radio access bearer, a QoS channel, or a QoS session.
 46. Thesystem recited in claim 1, wherein associate a particular serviceactivity of the wireless end user communications device with aparticular QoS connection comprises: identify an attempted or successfulcommunication associated with the particular service activity, andassociate the identified attempted or successful communication with aQoS level based on a QoS activity map.
 47. The system recited in claim1, wherein associate a particular service activity of the wireless enduser communications device with a particular QoS connection of theplurality of simultaneous QoS connections comprises identify a QoS rulefor an attempted or successful communication associated with theparticular service activity, and wherein assist in implementing a firsttraffic control comprises implement the QoS rule.
 48. The system recitedin claim 47, wherein the QoS rule directs the processor to pass, block,control, throttle, delay, defer, direct, route, forward, tunnel, orpriority queue a traffic flow associated with the attempted orsuccessful communication to one or more of a device QoS processingqueue, the particular QoS connection, a particular radio access bearer,a particular QoS channel, a particular QoS session, a particular networktunnel, a particular network logical channel, and a particular networkend point.
 49. The system recited in claim 47, wherein identify the QoSrule for the attempted or successful communication comprises: monitorthe attempted or successful communication; and identify the QoS rulebased on the monitored attempted or successful communication.
 50. Thesystem recited in claim 47, wherein the QoS rule is identified based ona QoS mapping associated with one or more of a particular application, aparticular network destination or end point, a particular traffic type,a network QoS availability level, a network congestion level and anetwork type.
 51. The system recited in claim 47, wherein implement theQoS rule comprises pass, block, control, throttle, delay, defer, direct,route, forward, tunnel, or priority queue the attempted or successfulcommunication.
 52. The system recited in claim 47, wherein the processorof the wireless end user communications device is further configured toobtain an update for at least an aspect of the QoS rule from a networkelement or a service controller.
 53. The system recited in claim 1,wherein assist in implementing a first traffic control comprises: obtaina first QoS rule associated with a first attempted or successfulcommunication associated with the particular service activity, andimplement the first QoS rule, and wherein the processor is furtherconfigured to: apply a second QoS rule associated with a secondattempted or successful communication associated with a second serviceactivity, and implement the second QoS rule.
 54. The system recited inclaim 53, wherein the second QoS rule differs from the first QoS rule,and wherein the first QoS rule directs the processor to pass, block,control, throttle, delay, defer, direct, route, forward, tunnel, orpriority queue a traffic flow associated with the first attempted orsuccessful communication to one or more of a device QoS processingqueue, the particular QoS connection, a particular radio access bearer,a particular QoS channel, a particular QoS session, a particular networktunnel, a particular network logical channel, and a particular networkend point.
 55. The system recited in claim 53, wherein the first QoSrule is obtained based on monitoring the first attempted or successfulcommunication.
 56. The system recited in claim 53, wherein the first QoSrule is obtained based on a first QoS mapping for a particularapplication, a particular network destination or end point, a particulartraffic type, a network QoS availability level, a network congestionlevel, or a network type.
 57. The system recited in claim 53, whereinthe first QoS rule is obtained based on information obtained with theassistance of a QoS application programming interface (API), the QoS APIcomprising an interface on the wireless end user communications devicefor communicating QoS information to or from an application on thewireless end user communications device.
 58. The system recited in claim53, wherein the first QoS rule is obtained based on first informationobtained from a first application with the assistance of a QoSapplication programming interface (API), and the second QoS rule isdetermined based on second information obtained from a secondapplication with the assistance of the QoS API, the QoS API comprisingan interface on the wireless end user communications device forcommunicating QoS information to or from the first and secondapplications.
 59. The system recited in claim 53, wherein the first QoSrule directs the processor to assist in delaying, deferring, timewindowing, queuing, prioritizing, throttling, or traffic shaping thefirst attempted or successful communication and the second QoS ruledirects the processor to assist in allowing or not interfering with oneor more communications associated with the second service activity. 60.The system recited in claim 53, wherein the processor of the wirelessend user communications device is further configured to obtain an updatefor at least an aspect of the first QoS rule from a network element or aservice controller.
 61. The system recited in claim 1, wherein theparticular service activity is a first service activity, and wherein theparticular QoS connection is a first QoS connection, and wherein theprocessor is further configured to: associate a second service activitywith a second QoS connection of the plurality of simultaneous QoSconnections; and assist in implementing a third traffic controlconfigured to control attempted or successful communications associatedwith the second service activity over the second QoS connection.
 62. Thesystem recited in claim 1, wherein the processor is further configuredto obtain at least an aspect of a QoS activity map from a userinterface, the QoS activity map providing an association of theparticular service activity with one or more QoS levels, and whereinassociate the particular service activity of the wireless end usercommunications device with the particular QoS connection of theplurality of simultaneous QoS connections comprises identify anattempted or successful communication associated with the particularservice activity and associate the identified attempted or successfulcommunication with a particular QoS level of the one or more QoS levels,and wherein assist in implementing the first traffic control comprisesobtain a QoS rule from the QoS activity map and apply the QoS rule toassist in implementing the particular QoS level for the attempted orsuccessful communication associated with the particular serviceactivity.
 63. The system of claim 62, wherein the particular serviceactivity comprises an attempted or successful network access associatedwith one or more of the following: an application, a networkdestination, a network source, a network end point, a uniform resourcelocator (URL), a website, a network server, a particular serviceprovider, a particular network type, a traffic type, a content type, anetwork protocol, a traffic session type, a QoS identifier, a time ofday, a state of network capacity, a network busy state, a user serviceplan authorization or standing, a roaming or home network status,voice-over-Internet-protocol (VOIP) traffic, streaming video traffic,differentiated access bandwidth during busy network periods, real-timeinteractive traffic, communications that include network connectedmultimedia meetings, communications that include shared presentations,communications that include pictures, communications that includevideos, communications that include voice, Internet browsing, shortmessage service (SMS) or push to talk, email message body delivery,email attachment delivery, communications associated with backgrounddownload services, communications associated with email downloads orother file transfers, communications associated with file transferprogram (FTP), communications taking place when the user is notinteracting with an application that is communicating with the network,communications associated with software updates, communicationsassociated with a best effort QoS level, communications associated withan interactive QoS level, communications associated with a QoS level fortime sensitive services, communications associated with a guaranteed bitrate QoS level, communications associated with a near real time orinteractive QoS level, and communications associated with a backgroundQoS level.
 64. The system recited in claim 62, wherein the particularservice activity comprises attempted or successful communicationsassociated with an application on the wireless end user communicationsdevice.
 65. The system recited in claim 62, wherein the one or more QoSlevels comprise a background service level.
 66. The system recited inclaim 62, wherein the particular service activity comprises an attemptedor successful communication associated with an application on thewireless end user communications device, and the one or more QoS levelscomprise a background service level.
 67. The system recited in claim 1,wherein the particular service activity is a background accessassociated with a particular application on the wireless end usercommunications device, and wherein the processor is further configuredto obtain a user input specifying to block the background accessassociated with the particular application, and wherein assist inimplementing a first traffic control comprises blocking the backgroundaccess.
 68. The system recited in claim 62, wherein the one or more QoSlevels comprise a background service level, and wherein the processor isfurther configured to assist in implementing the first traffic controlby implementing a QoS policy associated with the background servicelevel.
 69. The system recited in claim 1, wherein the first trafficcontrol comprises one or more of allowing, blocking, throttling,delaying, deferring, directing, routing, forwarding, tunneling, andpriority queuing the particular service activity.
 70. The system recitedin claim 1, wherein the second traffic control comprises allowing theparticular service activity.
 71. The system recited in claim 1, whereinat least one of the first traffic control and the second traffic controlis based on a user preference.
 72. The system recited in claim 1,wherein the first traffic control comprises blocking or restricting theattempted or successful communications associated with the particularservice activity, and the second traffic control comprises allowing ornot interfering with the attempted or successful communicationsassociated with the particular service activity.
 73. The system recitedin claim 72, wherein the first wireless access network is a cellularnetwork, and the second wireless access network is a wireless fidelity(WiFi) network.
 74. The system recited in claim 72, wherein the firstwireless access network is a roaming network, and the second wirelessaccess network is a home network.
 75. The system recited in claim 72,wherein the particular service activity comprises a background activity.76. The system recited in claim 1, wherein the first wireless accessnetwork is associated with a first cost, and the second wireless accessnetwork is associated with a second cost, the first cost being largerthan the second cost.
 77. The system recited in claim 76, wherein thefirst traffic control comprises blocking or restricting the attempted orsuccessful communications associated with the particular serviceactivity.
 78. The system recited in claim 1, wherein the processor isconfigured to assist in implementing the first traffic control byassisting in controlling a first QoS, and wherein the processor isconfigured to assist in implementing the second traffic control byassisting in controlling a second QoS.